SYSTEM AND METHOD FOR EU CONTEXT AND PDU SESSION CONTEXT MANAGEMENT

专利摘要:
systems and methods are provided for the grouping of eu, so that the eu can share a eu group context or share a pdu session context or both. in this way, the use of network resources, with respect to the eu context and pdu session context management, can be mitigated.
公开号:BR112020016723A2
申请号:R112020016723-1
申请日:2019-02-15
公开日:2020-12-15
发明作者:Ngoc Dung Dao；Xu Li
申请人:Huawei Technologies Co., Ltd.；
IPC主号:

专利说明:

[0001] [0001] This claim claims the priority benefit of the non-provisional order US serial number 15 / 898,442 filed on February 17, 2018, the contents of which are hereby incorporated by reference. FIELD OF THE INVENTION
[0002] [0002] The present invention generally belongs to the field of communication networks and particular modalities or aspects relate to the management of UE contexts and PDU session contexts. BACKGROUND
[0003] [0003] Based on the LTE network architecture, when a user equipment (UE) is turned on and connects to the network, the mobility management entity (MME) creates a UE context. MME assigns a unique short temporary identifier called SAE temporary mobile subscriber identity (S-TMSI) to the UE that identifies the UE context in the MME. This UE context contains user subscription information downloaded from the home subscription server (HSS). The local storage of signature data in the MME allows faster execution of procedures such as the establishment of a bearer, as it does not require consultation with the HSS every time. In addition, the UE context also contains dynamic information, such as the list of established carriers and the capabilities of the terminal. As would be easily understood, this UE context information is also used by a base station, for example, an evolved NodeB (eNB) associated with or connected to the UE, for example, UE eNB context which is a block of information in a eNB associated with an active UE.
[0004] [0004] In addition, a UE receives services through a protocol data unit (PDU) session, which is a logical connection between the UE and the data network. The UE requests the establishment of the PDU session and as such, in the present context, the UE has an associated UE context and a PDU session context, which must be stored and managed by the communication network in order to provide the UE with desired functionality.
[0005] [0005] The technical report of the 3rd Generation Partnership Project (3GPP) numbered TR 23.799 and entitled "Study on Architecture for Next Generation System", version 14.0.0, December 2016 (hereinafter referred to as TR 23.799), represents an approach to the design of a system architecture for next generation mobile networks, also known as 5th generation (5g) networks. In the proposed “next generation” (NG) networks, such as 5G wireless communication networks, additional flexibility and functionality are available for the network. In addition, it is proposed to have many more connections to the network, since the Internet of Things (IoT) brings connectivity to a new range of devices. In addition, on NG networks, it is possible for a UE to establish multiple PDU sessions for the same data network. As such, it is necessary to manage the use of network resources, for example storage, computing and signaling.
[0006] [0006] Therefore, there may be a need for a system and method for the management of UE contexts or PDU session contexts or both, which is not subject to one or more limitations of the prior art.
[0007] [0007] This background information is intended to provide information that may be of potential relevance to the present invention. No admission is necessarily intended, nor should it be interpreted, that any of the foregoing information constitutes the state of the art against the present invention. SUMMARY
[0008] [0008] It is an objective of the present invention to avoid or mitigate at least one disadvantage of the state of the art.
[0009] [0009] In accordance with an aspect of the present invention, a method is provided for selecting a network exposure function (NEF) on a communication network. The method includes obtaining, by an application function (AF), information about a UE and information about a set of NEFs, the set of NEFs including one or more NEFs, selecting, by the AF, a NEF based on the information obtained and applying, through the AF, the NEF selected to serve the UE.
[0010] [0010] In accordance with an aspect of the present invention, a network function is provided including a network interface for receiving data and transmitting data to network functions connected to a network and a processor. The network function also includes a non-transitory memory to store instructions that, when executed by the processor, cause the network function to be configured to obtain information about a UE and information about a set of NEFs, the set of NEFs including one or more NEFs , select a NEF based on the information obtained and impose the selected NEF to serve the UE.
[0011] [0011] In some modalities, the selected NEF is different from the original NEF that serves the UE before the selection of the selected NEF. However, it will be readily understood that the selected NEF may in fact be the same NEF as the original NEF in cases where an improved choice for NEF does not exist. According to the modalities, the application function (AF) provides information for a central function of common API structure (CAPIF), in which this information can be used for NEF selection. In some modalities, the central CAPIF function can provide a list of suitable NEFs from which the AF can select the NEF. It is easily understood that one or more of the above can be included in one embodiment.
[0012] [0012] In some modalities, obtaining information includes the receipt, by the AF, of an EU context of the UE. In some embodiments, the information in the NEF comprises one or more of the following: PLMN ID, DNN, DNAI (s); Application ID (s), service-identifier-AF; S-NSSAI, NSI- ID, EU group ID, including internal group ID, external group ID, IMSI group ID, EU ID, AF ID, IP address AF, FQDN AF, IP address UPF, FQDN , AMF ID, AMF IP address, AMF FQDN, SMF ID, SMF IP address and SMF FQDN. In some modalities, applying the NEF includes the signing, by the AF, of event exhibition services of the selected NEF and the sending, by the AF, of a request for routing influence traffic to the selected NEF. In some modalities, prior to selection, the method includes the signing, by the AF, of event exposure services from the originating NEF and the sending, by the AF, of a request for routing influence traffic to the originating NEF. In some modalities, after selection, the method includes canceling the subscription, by AF, of the event exhibition services of the
[0013] [0013] In accordance with an aspect of the present invention, a method is provided for selecting a network exposure function (NEF) on a communication network. The method includes selecting an NEF to serve a UE when receiving a trigger, the trigger resulting from one or more UE mobility, load balancing, relocating an NEF, denial of service attack, a re-selection request and applying a transmission of an UE context from the UE to the selected NEF.
[0014] [0014] In accordance with an aspect of the present invention, a network function is provided including a network interface for receiving data and transmitting data to network functions connected to a network and to a processor. The network function also includes a non-transitory memory to store instructions that, when executed by the processor, cause the network function to be configured to select a NEF to serve a UE when receiving a trigger, the trigger resulting from one or more of UE mobility, load balancing, relocation of an NEF, denial of service attack, a re-selection request, and impose a transmission of an UE context from the UE to the selected NEF.
[0015] [0015] According to some modalities, the selection is made by a session management function (SMF).
[0016] [0016] According to some modalities, the selection is made by a central function of common API structure (CAPIF). According to some modalities, the transmission is between the selected NEF and a UDR. It is easily understood that one or more of the above can be included in one embodiment.
[0017] [0017] In accordance with an aspect of the present invention, a method is provided for relocating the network exposure function (NEF) on a communication network. The method includes receiving, by an NEF, an UE context from an UE and subscribing, by NEF, a service of a control plan network function based on the UE context received from the UE.
[0018] [0018] In accordance with an aspect of the present invention, a network function is provided including a network interface for receiving data and transmitting data to network functions connected to a network and a processor. The network function also includes a non-transitory memory to store instructions that, when executed by the processor, cause the network function to be configured to receive a UE context from a UE and subscribe to a service of a network plan function. control based on the UE context received from the UE.
[0019] [0019] In some modalities, the service of the control plan network functions includes one or more of subscribing, by NEF, of event display services of a session management function (SMF), subscribing, by NEF, services event exposure function for an access management function (AMF), subscribe, by NEF, event display services for a unified data management function (UDM) and subscribe, for NEF, event exposure services for a function policy control (PCF). According to some modalities, the UE context of the UE is received from an originating NEF serving the UE or a unified data repository (UDR). In some embodiments, the NEF is selected by an application function (AF), or a session management function (SMF), or a central function of a common API structure (CAPIF) to serve the UE as a source NEF after the selection. It will be understood that the appropriate network function can be configured to perform the additional method steps mentioned above. It is easily understood that one or more of the above can be included in one embodiment.
[0020] [0020] In accordance with an aspect of the present invention, a method is provided for managing user equipment (UE) in a communication network. The method includes receiving, by a network function, a request from a UE, said UE belonging to a group of UE and generating, by the network function, a context of UE group.
[0021] [0021] In accordance with an aspect of the present invention, a network function is provided including a network interface for receiving data and transmitting data to network functions connected to a network and a processor. The network function also includes a non-transitory memory to store instructions that, when executed by the processor, cause the network function to be configured to receive a request from a UE, said UE belonging to a UE group and generate a context EU group.
[0022] [0022] According to some modalities, the EU group context includes an EU group identifier. According to the modalities, the UE group context includes one or more protocol data unit (PDU) session contexts and their PDU session identifiers. According to the modalities, the UE group context includes one or more session contexts of shared protocol data unit (PDU) and their identifiers. According to the modalities, the EU group context includes a list of EU IDs that are members of the EU group. It is easily understood that one or more of the above can be included in one embodiment.
[0023] [0023] In accordance with an aspect of the present invention, a method is provided for managing user equipment (UE) in a communication network. The method includes receiving, via a network function, a request including indicative data from an EU group and transmitting, through the network function, a notification, the notification based on the request and the data.
[0024] [0024] In accordance with an aspect of the present invention, a network function is provided including a network interface for receiving data and transmitting data to network functions connected to a network and a processor. The network function also includes a non-transitory memory to store instructions that, when executed by the processor, cause the network function to be configured to receive a request including data indicating an EU group and transmit a notification, the notification based in the request and data.
[0025] [0025] According to some modalities, the data includes a protocol data unit (PDU) session identifier. According to some modalities, the data includes a shared protocol data unit (PDU) session identifier. According to some modalities, the request includes a request to modify a shared PDU session and in which the notification includes a rejection. According to some modalities, the request includes a request for relocation of the network exposure function (NEF) and where the notification includes data indicative of an EU group context and where the EU group context includes one or more of a UE group identifier, protocol data unit (PDU) session identifier and a shared PDU session identifier. It is easily understood that one or more of the above can be included in one embodiment.
[0026] [0026] In accordance with an aspect of the present invention, a method is provided for selecting or re-selecting a network exposure function (NEF) on a communication network. The method includes receiving, through a destination application function (T-AF), an UE context, subscribing, through T-AF, event exposure services from a source NEF and sending, through T-AF, a request routing of influence traffic to the originating NEF. The method also includes, when determining a destination NEF, signing, by T-AF, event exposure services of the destination NEF and sending, by T-AF, a request for forwarding influence traffic to the destination NEF.
[0027] [0027] In accordance with an aspect of the present invention, a network function is provided including a network interface for receiving data and transmitting data to network functions connected to a network, a processor and a non-transitory memory for storing instructions. The instructions, when executed by the processor, cause the network function to be configured to receive a UE context, subscribe to event exposure services from a source NEF and send a request for routing influence traffic to the source NEF. The instructions, when executed by the processor, cause the network function to be configured to, after determining a destination NEF, subscribe to event exposure services from the destination NEF and send a routing request for influence traffic to the Target NEF.
[0028] [0028] According to some modalities, the method also includes canceling the subscription, by T-AF, for event exposure services of the originating NEF and canceling, by T-AF, the request for routing influence traffic with the Source NEF. It will be understood that the appropriate network function can be configured to perform the additional method steps mentioned above. It is easily understood that one or more of the above can be included in one embodiment.
[0029] [0029] In accordance with an aspect of the present invention, a method is provided for selecting or re-selecting a network exposure function (NEF) on a communication network. The method includes receiving, through a destination NEF, an EU context transfer request, subscriptions by the destination NEF, control plan network function services and sending a destination transfer response via the destination NEF. EU context.
[0030] [0030] In accordance with an aspect of the present invention,
[0031] [0031] According to some modalities, the subscription of control plan network function services includes one or more subscriptions, by the destination NEF, of event exposure services of a session management function (SMF), subscriptions , by the destination NEF, event display services from an access management function (AMF), subscriptions, by the destination NEF, event display services from a unified data management function (UDM) and subscriptions, by the destination NEF, of event exposure services from a policy control function (PCF). It will be understood that the appropriate network function can be configured to perform the additional method steps mentioned above. It is easily understood that one or more of the above can be included in one embodiment.
[0032] [0032] The modalities have been described above in conjunction with aspects of the present invention on which they can be implemented. Those skilled in the art will appreciate that the modalities can be implemented in conjunction with the aspect with which they are described, but they can also be implemented with other modalities in that aspect. When the modalities are mutually exclusive, or otherwise incompatible with each other, it will be evident to those skilled in the art. Some modalities can be described in relation to one aspect, but they can also be applicable to other aspects, as will be evident to those skilled in the art.
[0033] [0033] Some aspects and modalities of the present invention can provide a reduction in the use of network resources, with respect to the UE context and PDU session context management. BRIEF DESCRIPTION OF THE FIGURES
[0034] [0034] Other features and advantages of the present invention will be evident from the following detailed description, taken in combination with the accompanying drawings, in which: FIG. 1 illustrates a method for the context of UE and PDU session context management, in accordance with the modalities of the present invention; FIG. 2 is a method for the context of UE and PDU session context management, according to the modalities of the present invention; FIG. 3 is a diagram that illustrates a modality of interactions between the Management Plan, Control Plan and User Plan of a network; FIG. 4 illustrates a method for configuring EU group context according to the modalities of the present invention; FIG. 5 illustrates a method of creating UE group context triggered by a network management function according to the modalities of the present invention;
[0035] [0035] The present disclosure is directed to systems and methods for UE context and PDU session management. It was observed that with the increase in applications including IoT devices, there will be a great demand for communication network resources to provide a desired service level for this increased demand, for example, the storage and signaling required by the network in order to manage the UE context and PDU session context data for those UEs or electronic devices. In addition, it was noted that specific groups of UEs or electronic devices may have the same subscribed capabilities and services. Thus, systems and methods are provided for clustering UEs, so that the UEs can share an UE group context or share a PDU session context or both. In this way, the use of network resources, with respect to the UE context and PDU session context management, can be mitigated. It will be readily understood that, although it is considered that the term group can be used to define a plurality of UEs that share the same context, other terms can at least equally be used for example, collection of UEs or set of UEs.
[0036] [0036] According to the modalities, a UE requests that a new PDU session be established. A control plan (CP) function, for example a session management function (SMF), can evaluate the request and determine whether the new requested PDU session should be mapped to a new PDU session or to a PDU session existing shared network. This mapping can be performed in which the SMF can map the PDU session ID, which is generated by the UE when requesting the PDU session, to the new PDU session or to an existing PDU session that must be shared among several UEs .
[0037] [0037] According to the modalities, when sharing PDU sessions for a group of UEs, if a control plan (CP) network (NF) function needs to send one or more control messages or modifications to a plurality of sessions that all happen to be mapped to the shared PDU session, only a single control message would have to be sent to modify the shared PDU session, instead of control messages for each of the PDU sessions associated with the session. Shared PDU, or PDU sessions associated with UEs in an EU group. For example, the control plan function, for example a policy control function (PCF), session management function (SMF), access management function (AMF) or a network exposure function (NEF), it would just have to send a control message to modify the shared PDU session context instead of multiple control messages, each control message is to modify a PDU session context from an individual UE context. As such, according to the modalities, there may be a reduction in the use of network resources for managing the UEs and PDU sessions, for example a reduction in the necessary storage, computing and signaling. This reduction in the use of the network can also be considered a reduction in the internal operation of the UP and CP functions when modifying the parameters of a large number of UEs and PDU sessions.
[0038] [0038] According to the modalities, a method is provided for the context of UE and PDU session context management. With reference to FIG. 1, upon receiving 101 a request from an UE that is a member of an UE group for a network function, the network function proceeds to generate 102 an EU group context that is indicative of the UE group. For example, the UE context can include data indicative of an UE group identifier (ID), one or more PDU session identifiers, which can include PDU session identifiers and shared PDU session identifiers, and a list of EU IDs that are members of the EU group. In some embodiments, the UE group context may include indicative data on quality of service (QoS) or billing policies or both to be applied for PDU sessions or shared PDU sessions of UEs in the UE groups. According to the modalities, the network function can be an access management function (AMF), session management function (SMF), network exposure function (NEF), policy and control function (PCF), function user plan (UPF), Access Network ((R) AN) (Radio) node, Unified Data Repositor (UDR), Unified Data Management (UDM), Network Slice Selection Function (NSSF), Function From
[0039] [0039] According to the modalities, a method for the context of UE and PDU session context management is provided. With reference to FIG. 2, upon receiving 201 a request that includes indicative data from a UE group by a network function (NC), the network function proceeds to transmit 202 a notification in which this notification is based on the request and the data. For example, the data may include information indicative of an UE group, and the request is indicative of a modification of the service for the UEs that are included in the UE group. The indicative information of the UE group can be considered as part of the UE group context and the UE group context can include data indicative of one or more UE group identifiers (ID), one or more PDU session identifiers , one or more of the shared PDU session identifiers, and a list of UE IDs that are members of the UE group. In some embodiments, the UE group context may include indicative data on quality of service (QoS) or billing policies or both to be applied to a PDU session or shared PDU session of the UEs that are members of the EU group. According to the modalities, the network function can be AMF, SMF, NEF, PCF, UPF, (R) AN, UDR, UDM, NSSF, NRF, or other network functions.
[0040] [0040] In order to provide context for the instant application, which is directed to interactions between an UE and a communication network, FIG. 3 is provided to illustrate a network architecture 300 in which the resources of the operator network 302 are divided into a set of logical plans, a user plan (UP) 304, a control plan (CP) 306 and a management plan (MP) 308. UP 304 is typically focused on packet transport, but certain functions, including packet filtering and traffic shaping, can be performed on UP 304, although this is usually performed based on instructions from a network function in CP
[0041] [0041] UP 304 can also be referred to as a data plan. It carries traffic between an ED 399 and external data networks (not shown) or functions within the operator network. The UP 302 is usually composed of user plan functions (UPFs) 314. As would be readily understood in some cases, an ED can be a user device (UE). In some cases, an UPF 314 can be specific to a specific UE, it can be specific to a specific service (in some modalities, it can be specific to the user and the service), and in other cases it can be a generic function that serves a plurality of users and services. UPFs 314 are connected to each other to allow data plan traffic to be transmitted. As would be easily understood, there are one or more (R) AN nodes that are positioned between the UE and the UPF, which can at least in part provide interconnectivity between them.
[0042] [0042] The 306 control plan can consist of 316A control plan (CPF) functions. In a 3GPP-compatible network, some 316A control plan functions have functions defined by standards, while other 316B control plan functions may be outside the specification of the relevant standards. This can effectively result in the 306 control plan being divided into a 306A compliant control plan segment and a 306B compliant control plan segment. Accordingly a 306A 3GPP control plane segment, 316A network functions, such as an AMF, SMF, NEF, authorization and security function (AUSF), etc., may be present, and in some embodiments more than an example any or all of the functions may be present. In a control plan segment not compliant with 306B standards, a 316B network function, such as a function to perform a software-defined network controller (SDN), or other controllers including a self-creating virtual network-oriented operation controller services (SONAC-Ops), can be instantiated. The control plan functions 316 can be connected to other CPFs, as shown by functions 316A, but this is not necessarily necessary, as can be seen by CPF 316B. ED 399 can also communicate with CPFs.
[0043] [0043] The management plan 308 can be divided between a section compliant with standards 308A and a section 308B not compatible with standards, as far as CP 306 is divided. Within the MP 308, network functions and nodes 318 can communicate with each other, and with a network function or node 312 within the customer domain 310. The entities in the 318A management plan (within the standardized section 308A) and 318B (within the section not compliant with 308B standards) can be used to establish the policy and the mechanisms by which the policy should be applied, based on the available resources and requirements received from the 312 client (and possibly a plurality of clients many different). The network management functions (NMF) 318 can be responsible for the accounting and billing functions, for element management, they can provide the necessary services for an operation support system (OSS) and a business support subsystem (BSS ). Outside of standardized functions, 318B non-standard network functions may include a network function virtualization management and orchestration system (NFV-MANO) and a service-oriented virtual network composition controller (SONAC-Com).
[0044] [0044] NMFs 318 can receive external input from a client node 312, and can communicate with each other. NMFs 318 can also communicate, via any of the MP-CP 320 connections, with CPFs 316 to provide instructions on policies to be applied by CPFs
[0045] [0045] In some embodiments, the client network function 312 may have a connection to a CFP 316. This CPF, with which the client network function 312 communicates, may be a CPF 316A compatible with 3GPP or a CPF 316B not compatible with 3GPP. In alternative embodiments, the client network function 312 can make use of a function within the management plan 308 to relay messages to functions in the control plan 306. Within client domain 310, there may be an optional control plan 324, with client control plan functions 326 and 328. When such client control plan 324 is present, functions 326 and 328 can have logical communication links with one or both of ED 399 and client network function 312. The client control plan functions 326 and 328 can have connections to functions within the 306 control plan (functions compatible with 3GPP 316A or functions 316B not compatible with 3GPP).
[0046] [0046] According to the modalities, the UE group context is created in control plan functions that can include AMF, SMF, PCF, UDM, UDR, NEF, NSSF, NRF and the application function (AF). The UE group context is also created in user plan functions that can include the access network (radio) node ((R) AN), access node (AN) and UPF. It will readily be understood that while the term UE group context is used to define a plurality of UEs that share the same context, other terms can at least equally be used to define the same resource, for example, shared UE context, context of EU collection, EU set context or similar.
[0047] [0047] According to the modalities, the UE group context can be created in advance, for example by preconfiguring the UDM or UDR or by a network management function (NMF) with the necessary information related to the group context of EU. For example, the UE group context may include information related to one or more of: UE group identifier (ID), list of member EU IDs, PDU session group IDs, quality of service (QoS), collection policies or other resources within the EU group context that is associated with each of the member UEs. According to the modalities, the UE group context can be created by the control plan functions and the user plan functions after receiving a request, such as a request from the AF, or the UE, or the MFN.
[0048] [0048] According to the modalities, several different UEs are defined as members of a particular EU group, and that EU group can have an associated EU group ID. According to the modalities, an EU group context can be created by the AMF. In this case, when a first UE from a given EU group registers on the communication network, the MFA can create the EU group context in the MFA. According to some modalities, when a first UE from a given UE group requests a PDU session, there is an associated PDU session context. In cases where this PDU session context can be shared, for example, as a shared PDU session context, SMF creates an UE group context in SMF. SMF further requests that (R) AN, and UPF to establish an EU group context and / or shared PDU session context. According to some modalities, when the AF sends the first request to the NEF to an EU group, the EU group context is created in the NEF. In some embodiments, when a foreground control function, for example AMF, SMF or PCF, subscribes to NEF for the notification service for events or actions relevant to a particular EU group, the EU group context is created at NEF. As the UE group context is created and stored in the NEF, this can provide a reduction in the necessary signaling.
[0049] [0049] According to some modalities, the NEF is preconfigured to serve a particular UE group and the AF can send a request to the NEF in order to initiate the NEF by transmitting a request to configure an UE group context. For example, with reference to FIG. 4, AF 425 sends 401 an AF request, where this request carries information from UEs that are members of a given UE group. 101The request may include a transaction ID to represent this request, and information including one or more of: an external group identifier to identify the UE group, a list of external EU IDs or GPSI (Generic Public Subscription Identifier), a set of packet filters or Packet Flow (PFD) description to identify downlink traffic destined for one or some or all UEs in the UE group (for example, application server IP address (es) or IP), port numbers, QoS information (e.g. maximum bit rate for each UE, maximum aggregate bit rate for all UEs, packet delay budget, packet error rate), DNAI (data network access identifier).
[0050] [0050] NEF 424 subsequently sets up an EU group context for that particular EU group. An authentication and authorization procedure 402 is initiated between AF 425, NEF 424, AUSF 423 and UDM 422 or UDR or both. During procedure 402, the UDM or UDR can assign an internal group ID, which is mapped to the external group ID. The UDM or UDR informs NEF 424 of the internal group ID. Upon completion of the 402 authentication and authorization procedure, NEF 424 broadcasts 403 an AF request response that may indicate that the control plan is configuring the UE group context.
[0051] [0051] NEF 424 subsequently selects 404 UDM / UDR 422 for the configuration of the UE group context. NEF 424 sends 405 a request to update application data indicative of the EU group context to UDM / UDR 422. NEF 424 can provide some or all of the information received from AF 425, such as the packet filter set or PFD, and QoS requirements information for the UDR.
[0052] [0052] The UDM and / or UDR can send a 406 reply message to the NEF. The response message can include the internal group ID if this parameter was not sent in procedure 402.
[0053] [0053] UDM / UDR 422 transmits 407 an application data change notification that is indicative of the UE group context to PCF 421. Message 407 can include internal group ID, application ID, PFD or sets of packet filters for both uplink (UL) and downlink (DL) directions, QoS parameters authorized for member UEs (such as maximum bit rate (MBR), maximum flow bit rate (MFBR), rate guaranteed bit rate (GFBR), session-aggregated maximum bit rate (AMBR), packet delay budget (PDB)) and for the UE group (e.g. UE group -AMBR), collection policy (for example, group-based EU charging where charging is applied to all UEs in the EU group as a whole, not individual UEs).
[0054] [0054] If message 407 carries notification of data change and only the internal group ID only, PCF 421 can send a request to the UDM and / or UDR to provide the internal group ID data. PCF 421 can generate in step 408 new EU-related policies and policies related to EU groups using the information provided by UDM / UDR 422. PCF 421 subsequently transmits 409 a policy update notification to SMF 420, which currently serves UE group UEs, where the policy update notification is indicative of the UE group context. PCF 421 can also send other messages (not shown in FIG, 4) to other network entities, such as AMF (which currently serves UEs in the UE group) to update access and mobility policies, to the UE for selection policy EU route map (URSP). CP functions can create EU group context after receiving EU group information from the PCF. PCF 421 can also send notification message to NSSF, which includes internal group ID and UEs that are members of the internal group. When a CP role is selected later, the NSSF can use the information from the UE group to make sure that the same SMF or AMF is used to serve all UEs in the EU group that are currently associated with (R) AN nodes who are in the same service area as AMF or in the same service area as SMF.
[0055] [0055] According to some modalities, the messages exchanged between the NFs in FIG. 4 and other figures as present in the instant application, can be implemented alternatively using existing or new NF service-based interface services.
[0056] [0056] FIG. 5 illustrates a method of creating UE group context triggered by a network management function according to the modalities of the present invention. The network management function (NMF) 508 sends 511 to UDM (or UDR) 506 a message as a request to create / modify / delete an internal UE group. The message can include the list of EU IDs (for example, permanent equipment identifier (PEI), permanent subscriber identifier (SUPI), IMSI, GPSI), or network slice information (for example, S-NSSAI, NSSAI), device owner identifier,
[0057] [0057] Optionally, in some modalities, for the creation of UE group context, UDM 506 can use the network function information provided by NMF 508 to identify CPF 502. Alternatively, UDM can discover the CP function getting information from the network repository (NRF) function. If the UE group context was created in CPF 502, the CPF can register with the UDM. The UDM can provide EU group updates for CPF 502 by modifying / deleting messages.
[0058] [0058] According to the modalities, once CPFs are selected to serve a specific EU group, UDM can inform NRF which CP functions are selected to serve the EU group. The UDM message to the NRF can include the EU group ID, application ID and EU ID. Information about the UE group and EU IDs, application ID and other information available in the NRF (such as network slice information) can be used for selecting NF CP, such as AMF, SMF and PCF, so that the same set of CP NFs can be selected to serve all UEs in an EU group in some geographical area, or in the same registration area managed by a specific MFA. In some embodiments, EU group information (for example, including EU group ID, EU group EU IDs, application ID) can be preconfigured by NMF 508 in NRF.
[0059] [0059] With further reference to FIG. 5, CPF 502 sends 517 to UDM 506 a message as an EU group creation / modification / deletion response to the message received. CPF 502 can send 518 to PCF 504 a message as an EU group policy creation / modification / deletion request. According to the modalities, for a new EU group, the CPF requests the PCF to send EU group policies. Policies may include policies that apply to all UEs in the group of UEs and / or policies that apply to individual UEs. CPF also registers with the PCF for policy updates. According to the modalities, for an existing EU group, if the PCF does not send policy updates to the CPF, the CPF can request that the PCF send updated policies. According to the modalities, if the EU group is excluded, the CPF may request that the PCFs remove their subscription from the PCF policy update services. PCF 504 sends 519 to CPF 502 a message as an EU group policy creation / modification / deletion request to confirm receipt of the message.
[0060] [0060] According to some modalities, the EU group context includes information indicative of the EU group ID, a list of EU IDs of each EU that is a member of the EU group and a list of session group IDs of PDU. In this embodiment, a UE may have a particular PDU session ID associated with it, where this PDU session ID is mapped to a PDU session group ID. The PDU session group ID identifies a PDU session that is shared among several UEs that are assigned to the UE group ID. Since all UEs within the group do not necessarily share the same PDU session with a particular PDU session group ID, there can be multiple PDU session group IDs associated with a particular UE group context. According to the modalities, the PDU session context, which can be associated with a particular UE, can include information indicative of PDU session information and a mapping between the PDU session ID with the associated UE group ID and PDU session group ID.
[0061] [0061] According to some modalities, the EU group context includes information indicative of a list of EU IDs of each EU that is a member of the EU group, information related to the EU group that may include one or more Quality Service, billing policies and other information related to the HU group. The UE group context may further include information indicative of the shared PDU session context that can be identified by the shared PDU session ID that is generated by the SMF. In these modalities, each UE has a UE context that includes a PDU session context and a shared PDU session context. In addition, the shared PDU session context includes a mapping of the PDU session ID generated by the UE with the UE group ID and the shared PDU session ID. According to these modalities, the configuration of an UE group context and shared PDU session context can be applied to UEs, for example, smartphones or other wireless devices, which have enhanced mobile broadband applications (eMBB) and massive IoT (MIoT) applications. In some cases, these applications can occur at the same time.
[0062] [0062] According to some modalities, the EU group context includes information that is indicative of the individual EU contexts of the UEs that have been assigned to the EU group, information related to the EU group that may include one or more Quality of Service, billing policies and other information related to the HU group. The UE group context may further include information indicative of the shared PDU session context that can be identified by the shared PDU session ID that is generated by the SMF. According to these modalities, the configuration of a UE group context can be applied to UEs that relate to one or more applications, such as massive IoT applications (MIoT).
[0063] [0063] According to the modalities, the UE context can include PDU session pointers pointing to memories of unshared PDU sessions and shared PDU sessions. PDU session pointers from multiple UE contexts can point to the same memory as shared PDU sessions. (R) AN, UPF, AMF, SMF and other functions have a mapping of PDU session ID generated by UE and PDU session ID generated by SMF. (R) AN, UPF, AMF and other functions can use the SMF address (such as IP address or FQDN) and shared PDU session ID to find the data for the shared PDU session. SMF uses the shared PDU session ID to find the context data for the shared PDU sessions.
[0064] [0064] According to the modalities, one or more of the following parameters can be stored in the context of PDU session of the UE context in SMF, AMF, UPF and (R) AN. The type of PDU session can be stored in the context of a PDU session, for example, an unshared PDU session or a shared PDU session. The PDU session ID can also be present in the PDU session context, for example, for an unshared PDU session, the PDU session ID can be generated by UE. For a shared PDU session, the PDU session ID can be generated by UE and generated by SMF. The PDU session pointer can be stored in the context of the PDU session. For an unshared PDU session, the PDU session pointer can point to a memory separate from the PDU data structure. For a shared PDU session, the PDU session pointer can point to a common memory of the PDU data structure. For example, the UE group ID and shared PDU session ID can uniquely identify the mapping between UE generated session ID and SMF generated shared PDU session ID. An example of a pointer could be an UE-generated PDU Session ID mapped to <UE Group ID, SMF-generated PDU Session ID>. The type of UP connection can be stored in the context of the PDU session, where the UP connection can be shared or not shared. According to some modalities, the PDU session context may include additional information elements, such as SMF ID (or SMF address) or AMF ID (or AMF address), depending on the network functions.
[0065] [0065] In addition to the individual EU context, AMF, SMF, (R) AN and UPF and other network functions may have an EU group context. The UE group context can include information elements that include one or more of the UE group ID, UE members, shared PDU session ID, SMF ID service (or address), AMF ID service ( or address), S-NSSAI and the UP connection type. The UE group ID can be unique in a PLMN or unique in a slice of the network. UE members can be a list of EU IDs from the EU group. The shared PDU session ID can be the ID generated by the service SMF and can be unique within an UE group. The service SMF can have an SMF ID (or address) and the service AMF can have an AMF ID (or address). The S-NSSAI can represent network slice information and the type of UP connection can be shared or not shared.
[0066] [0066] According to the modalities, in (R) AN, UPF, AMF, SMF and other network functions, UE information can be stored in a separate UE context or in an EU group context or in a separate EU context and an EU group context. If the UE has an unshared PDU session, the UE information can be stored in a separate UE context. If the UE belongs to an UE group, the UE information can be stored in an UE group context. The UE group context can include individual UE context profiles of all UEs in this group. Alternatively, the UE context profile can have pointers pointing to the UE group context profile.
[0067] [0067] According to some modalities, when all UEs in an EU group have only shared PDU sessions, it is more efficient to have a single EU group context in the UP and CP functions. The UE group context contains all the individual UE information. When the 5G CP or UP functions wish to make changes to all UEs in the UE group, the UE group ID can be used to send messages to all UEs in the UE group. The UE group context includes the UE context of all member UEs. The UE group context can include an UE group ID that can be unique within a PLMN or unique within a network slice instance; EU members, which can be a list of EU member IDs; UE context of each UE member that can include a security context, except for a shared PDU session context; shared PDU session contexts that can define the PDU sessions that are shared between UEs in the UE group; and policies applied to shared PDU sessions, for example, policies for individual UEs and groups of UEs.
[0068] [0068] According to the modalities, when a control plan function or a user plan function must transmit a message or signal to an EU group, the message or signal may include information that is indicative of the group ID of UE and the shared PDU session ID. In this way, by sending a single message, the operation of several UEs and their associated PDU sessions can be modified, thus reducing the signaling that is necessary to make these changes in the operation of the network.
[0069] [0069] However, in some modalities, if a particular UE requests a modification to a PDU session associated with it, and this PDU session is a shared PDU session, that is, multiple UEs are using the same PDU session , the control network can reject this requested modification. For example, if an UE requests changes to certain PDU session control parameters, for example, allocation and retention priority (ARP), maximum bit rate packet delay, or other control parameters that can result in changes to the session of PDUs that would affect other UEs, the control network will reject the requested modification.
[0070] [0070] According to the modalities, the shared PDU session ID is generated by a control plan function, for example, SMF, which can be associated with a plurality of specific PDU sessions being used by several UEs and there is no change from the UE. For example, a UE may request the establishment of a new PDU session that has a PDU session ID generated by UE. The control plan function, for example SM, can associate or map this PDU session ID generated by UE with a PDU session ID generated by SMF, for example, a shared PDU session ID. It is understood that the shared PDU session ID can be unique within the particular SMF, unique within a plurality of SMFs associated with the communication network, or unique within a network slice instance, or unique in relation to the PLMN network . In addition, it will be understood that, although these modalities have been discussed in relation to SMF, SMF can be replaced by another control plan function, for example, AMF, PCF, UDM, NEF or the like.
[0071] [0071] FIG. 6 illustrates a procedure for registering a UE with an (R) AN according to the modalities of the present invention. According to the modalities, the procedure illustrated in FIG. 6 provides a method for creating EU group context in MFA when the first EU of an EU group registers with the NC. When the UE performs the initial connection, the UE can send the device class to the (R) AN and the (R) AN can inform the AMF about the device class of the UE. It is understood that the device class can also be referred to as the EU device class. The UDM provides EU group ID and EU ID members. PCF provides EU group policies. The MFA can request (R) AN to create an EU group context, which stores the EU group's access and mobility policies.
[0072] [0072] With reference to FIG. 6, the method includes the sending by the UE 621 of a message as a registration request for the (R) AN 604. The message can include (AN parameters, RM-NAS registration request (registration type, SUPI or 5G-GUTI , security parameters, NSSAI, UE 5GCN capacity, PDU session state, PDU session (s) to be reactivated, device class UE, follow on demand, and MICO mode preference)). In the case of 5G-RAN, AN parameters can include, for example, SUPI or 5G-GUTI, the selected network and NSSAI, device class UE.
[0073] [0073] If a SUPI is included or the 5G-GUTI does not indicate a valid AMF, the (R) AN, based on the device class (R) AT and NSSAI and / or UE, if available, selects an AMF 622. The process by which (R) AN selects an MFA can proceed as it is known. If (R) AN is unable to select an appropriate AMF, it forwards the registration request to an AMF that has been configured, in (R) AN, to perform the AMF selection. In some embodiments, the MFN can pre-configure the EU group information on (R) AN 604 with the following information: EU group ID, EU group EU IDs, network slice information (e.g.
[0074] [0074] The (R) AN 604 sends 623 a message as a registration request for the new AMF 606. The message can include (parameters N2, RM-NAS registration request (registration type, permanent subscriber identifier or 5G- GUTI, security parameters, NSSAI and MICO mode preference, device class UE)). When 5G-RAN is used, the N2 parameters include the location information, cell identity and the type of RAT related to the cell in which the UE is camped. When NG-RAN is used, the N2 parameters also include the cause of establishment. The message at 623 can include EU group information (such as EU group ID). If the type of record indicated by the UE is periodic record update, then steps 624 to 637, referred to below, can be omitted.
[0075] [0075] In some modalities, the new AMF 606 sends 624 a message as a request for transfer of UE context to the old AMF 608. The message can be Namf_Communication_UE_Context_Transfer (complete registration request). If the UE's 5G-GUTI was included in the registration request and the service AMF has changed since the last registration, the new AMF can invoke the Namf_Communication_UEContextTransfer service operation in the old AMF including the full IE registration request, which can be protected by integrity, to request the SUPI and MM context of the UE. The former AMF uses the full IE integrity-protected registration request to verify that the context transfer service operation invocation matches the requested UE. The old AMF also transfers event subscription information from each consumer NF to the UE for the new AMF. Subsequently, the old AMF 608 sends 625 a UE context transfer response which can be a response to Namf_Communication_UEContextTransfer which can include (SUPI, Context MM, SMF information). The old AMF can respond to the new AMF for the Namf_Communication_UEContextTransfer invocation including the SUPI and MM context of the UE. If the old AMF contains information about active PDU sessions, the old AMF will include SMF information, including SMF identities and PDU session identities. If the old AMF contains information about active N2AP UE-TNLA connections to the N3IWF, the old AMF will include information about the N2AP UE-TNLA connections.
[0076] [0076] In some modalities, the new AMF 606 sends 626 an identity request to the UE 602. If the SUPI is not provided by the UE nor retrieved from the old AMF, the identity request procedure is initiated by the AMF by sending a message of identity request to the UE. UE 602 can send 627 an identity response to the new AMF where the identity response can include the SUPI. In some embodiments, AMF 606 may decide to invoke an AUSF 628, in which AMF, based on SUPI, can select an AUSF as it is known. AUSF can initiate 629 authentication of the UE. If network slicing is used, the AMF can decide whether the registration request needs to be redirected. AMF can also initiate security functions NAS.
[0077] [0077] In some modalities, the new AMF 606 sends 630 a message to the old AMF 608 in which the message is a Namf_Communication_RegistrationCompleteNotify (). If the AMF has changed, the new AMF notifies the old AMF that the registration of the UE in the new AMF is complete by calling the Namf_Communication_RegistrationCompleteNotify service operation. If the authentication / security procedure fails, the Registry must be rejected and the new AMF invokes the Namf_Communication_RegistrationCompleteNotify service operation with a rejection indication reason code for the old AMF. The former AMF continues as if the EU context transfer service operation had never been received. In some embodiments, the new AMF 606 sends 631 an identity request to the UE 602. If the PEI was not provided by the UE or retrieved from the old AMF, the identity request procedure is initiated by the AMF by sending an identity request message to the UE to recover the PEI.
[0078] [0078] In some embodiments, the new AMF 606, based on the SUPI or EU device class or both, selects 633 a UDM 616. If the AMF 606 knows that the UE belongs to an EU group, the AMF 606 can select the same UDM 616 that serves other UEs in the same UE group. If the AMF has changed since the last registration, or if the UE provides a SUPI that does not refer to a valid context in the AMF, or if the UE registers with the same AMF, it has already registered with non-3GPP access (ie, the UE is registered in a non-3GPP access and initiates this registration procedure to add a 3GPP access), the new AMF 606 invokes 634a service operation
[0079] [0079] In some modalities, the new AMF 606, based on SUPI, selects a PCF in 635. If the AMF 606 knows that the UE belongs to an EU group, the AMF 606 can select the same PCF 610 that was selected (or pre-configured) to serve the UEs of the UE group. The new AMF 606 sends 636 a message to PCF 610, where the message is an Npcf_PolicyControl_PolicyCreate (SUPI). If the AMF has not yet obtained the access and mobility policy for the UE or if the access and mobility policy in the AMF are no longer valid, the AMF asks the PCF to apply operator policies for the UE by creating a policy control session with the PCF through the Npcf_PolicyControl_PolicyCreate service operation. In the case of roaming, the interaction between H-PCF and V-PCF is necessary to make the access and mobility policy available. The PCF sends a response to the new AMF where the response is an Npcf_PolicyControl_PolicyCreate (access and mobility policy data). The PCF responds to the Npcf_PolicyControl_PolicyCreate service operation and provides the access and mobility policy data for the UE to the MFA.
[0080] [0080] In some modalities, the new AMF sends a message to SMF in which the message is a Namf_EventExposure_Notify (). The AMF invokes Namf_EventExposure_Notify in one or more of the following situations: 1) If the AMF is changed, the new AMF notifies each SMF of the new AMF serving the UE, informing the reachability status of the UE, including the PDU session state of the Relevant EU for each SMF.
[0081] [0081] According to the modalities, the new AMF sends 638 an N2 Request () to N3IWF 618. The AMF may decide to modify the EU-TNLA N2AP connection to N3IWF. This is done in case the AMF is changed and the old AMF has N2AP UE-TNLA connections to an N3IWF for the UE. N3IWF 618 can send 639 an N2 Response () to the new AMF 606.
[0082] [0082] In some modalities, the former AMF 608 sends 640 Npcf_PolicyControl_PolicyDelete () to PCF 610. If the former AMF previously requested that the UE context be established in the PCF, the former AMF ends the UE context in the PCF by invoking the operation of service Npcf_PolicyControl_PolicyDelete. PCF 610 can send an Npcf_PolicyControl_PolicyDelete () response to the old AMF
[0083] [0083] According to the modalities, the new AMF 606 sends 641 a registration acceptance message to the UE
[0084] [0084] In some modalities, AMF 606 sends 642 to (R) AN 604 a message to establish the UE context. The message includes EU device class, 5G GUTI, S-NSSAI, EU group context information (EU group ID, EU group EU ID, application ID, EU group access and policies of mobility), security information. If the UE group context was created by a shared PDU session preconfiguration procedure, (R) AN associates the UE with the UE group context. The UE group context can contain a pre-configured N3 shared tunnel. If the EU group context does not exist, MFA can send EU group context information to (R) AN, including EU group access and mobility policies. The MFA can include the list of UEs (including SUPI of UEs) of the same UE group ID. AMF may also include security information for (R) AN. (R) AN 604 sends 643 a reply message to AMF 606. If the UE group context does not exist, (R) AN can create DL
[0085] [0085] In some embodiments, UE 602 sends 644 a complete registration message to AMF 606. The UE sends a complete registration message to AMF to confirm that a new 5G-GUTI has been assigned. When the "PDU session (s) to be reactivated" is not included in the registration request, the MFA releases the signaling connection to the UE. When on-demand tracking is included in the registration request, AMF cannot release the signaling connection immediately after completing the registration procedure.
[0086] [0086] FIG. 7 illustrates a PDU session establishment requested by UE for non-roaming and roaming with local interruption in accordance with the modalities of the present invention. According to the modalities, methods are provided to create EU group context in SMF and UPF functions. In these modalities, the shared PDU session is not pre-configured. The UE sends a request to SMF to establish a PDU session after successful registration. AMF and SMF create shared PDU session context upon receiving the PDU session establishment request from the first UE of the UE group ID. FIG. 7 illustrates a method used to establish a new PDU session, as well as to deliver an existing PDU session between 3GPP access and non-3GPP access. In the case of roaming, the AMF determines whether a PDU session should be established in local outage (LBO) or home routing. In the case of LBO, the procedure is the same as in the case of non-roaming, however the SMF, UPF and PCF are located within the visited network.
[0087] [0087] With further reference to FIG. 7, there is an assumption that the UE has already registered with the MFA, so the
[0088] [0088] According to the modalities, AMF 706 determines that the message corresponds to a request for a new PDU session based on this type of request indicates "initial request" and that the PDU session ID that is not used for any existing UE PDU session. If the NAS message does not contain an S-NSSAI, AMF can determine a standard S-NSSAI for the requested PDU session under the UE signature, if it contains only a standard S-NSSAI or based on operator policy. The AMF selects 722 an SMF. The AMF stores an association of the PDU session ID and the SMF ID. The case where the request type indicates
[0089] [0089] According to the modalities, AMF 706 sends 723 an Nsmf_PDUSession_CreateSMRequest that can include (SUPI, DNN, S-NSSAI, PDU session ID, AMF ID, request type, device class, group ID of UE, existing shared PDU session IDs, N1 SM (PDU Session Establishment Request) information, user location information, access technology type, PEI, PCF ID, UE group information (e.g. , UE) for SMF 710. The PCF ID is the PCF ID that was selected by AMF 706 to serve the UE or to serve all UEs in the UE group. The AMF ID uniquely identifies the AMF that serves the UE AMF forwards the PDU session ID along with the N1 SM information containing the PDU session establishment request received from the UE The device class can be optional. SMF can obtain the device class later when accessing the UDM Based on one or more of S-NSSAI, device class and DNN, the AMF can select an UE group ID and include existing shared PDU session IDs from this UE group. The UE group ID (s) indicates that the UE belongs to an UE group. If SMF has already obtained UE subscription data, session management, QoS and billing policies for the UE group ID, SMF may not need to access the UDM or PCF to obtain the UE information.
[0090] [0090] In some modalities, if the SMF has not yet been registered and the subscription data is not available, then the SMF 710 registers 724a-724b with UDM 714, retrieves the subscription data and signs to be notified when the data of the subscription are modified. If the request type indicates "existing PDU session", SMF determines that the request is due to the transfer between 3GPP access and non-3GPP access. The SMF identifies the existing PDU session based on the PDU session ID. Subscription data includes the authorized PDU type (s), authorized SSC mode (s), standard 5QI / ARP, signed AMBR session, EU group ID, user group AMBR HUH. SMF verifies that the UE request is compatible with user signature and local policies. If the DNN matches an LADN, the SMF checks whether the UE is located within the LADN service area based on the AMF's UE location report. If this is not the case, the SMF rejects the UE request via NAS SM signaling by responding to the AMF with Nsmf_PDUSession_CreateSMResponse including a relevant SM rejection cause. The SMF tells the AMF that the PDU session ID should be considered as released, it unregisters the UDM and the rest of the method is ignored. The UE group AMBR is the maximum aggregated bit rate of the UE group ID. The group AMBR is applied by (R) AN and UPF. If the UE belongs to a group of
[0091] [0091] According to some modalities, UDM 714 can inform SMF 710 about PCF 712, which was selected by AMF 706 to serve the UE.
[0092] [0092] According to the modalities, if the SMF needs to perform authorization / secondary authentication 725 during the establishment of the PDU session by a DN-AAA server, the SMF selects a UPF and triggers the authentication / authorization of the establishment of the session. PDU. If PDU session authentication / authorization fails, SMF terminates the PDU session establishment procedure and indicates a rejection to the UE. Secondary authorization / authentication can be applied to individual UEs of the same UE group ID.
[0093] [0093] According to the modalities, if the dynamic PCC is implemented, SMF 710 performs the selection of PCF 726a. The SMF can select the same PCF that can be defined by AMF 706 in message 723 or defined by UDM 714 in step 724. If the dynamic PCC is not deployed, SMF can apply the local policy. The SMF can use one or both EU group ID and device class to select a PCF.
[0094] [0094] According to the modalities, if the request type indicates "initial request", the SMF selects an SSC mode for the PDU session. If step 725 is not performed, SMF 710 also selects a UPF 727. In the case of the IPv4 or IPv6 PDU type, the SMF allocates an IP address / prefix for the PDU session. For the unstructured PDU type, SMF can allocate an IPv6 prefix for the PDU session and N6 point-to-point tunneling (based on UDP / IPv6). If the request type indicates "emergency request" or "existing emergency PDU session", SMF selects the UPF according to the type of request. For the first UE of an EU group ID requesting the establishment of a PDU session, the SMF can allocate an IP address or IP prefix for the point-to-point PDU session and N6 IP / UDP tunnel. SMF can also assign an N6 IP / UDP tunnel flow label. For other UEs of the same UE group ID requesting PDU, SMF can allocate a new IP address or IP prefix for the point-to-point PDU session and N6 IP / UDP tunnel. Alternatively, SMF can use the same IP address / IP prefix for the N6 IP / UDP tunnel, but assign another flow label for the N6 IP / UDP tunnel for the PDU session for each UE. SMF can select shared UL and DL UP connections based on EU mobility information received from AMF, QoS and billing policies and legal interception requirements. The following combinations of tunnels N3 and N9 and N6 are possible, but are not limited to: 1) Tunnels UL and DL N3 and N9 are shared; 2) UL N3 and N9 tunnels are shared and DL N3 and N9 tunnels are not shared; 3) The N6 tunnel is shared or not shared.
[0095] [0095] According to some modalities, SMF 710 can select the same UPF 708 to serve the UEs of the EU group. If an intermediate UPF (I-UPF) (not shown in FIG. 7) is required to provide a connection between the (R) AN 704 and the UPF PDU (PSA) session anchor, the SMF 710 can select the same I- UPF to serve UEs that are in the I-UPF service area or in the PSA UPF service area
[0096] [0096] According to the modalities, SMF 710 can invoke 728a the Nsmf_EventExposure_Notify service operation to report an event to the PCF that was previously signed. If the request type is "initial request" and the dynamic PCC is deployed and the PDU type is IPv4 or IPv6, SMF will notify the PCF (which was previously signed) with the allocated UE IP address / prefix. PCF can provide authorized session AMBR and authorized 5QI / ARP for SMF. For the UE group, the SMF can notify the PCF about the IP address or IP prefix of the UE and / or IP address / IP prefix of the N6 IP / UDP tunnel. The PCF has an IP address prefix mapping of UEs from the same UE group. PCF 712 can provide updated policies for SMF by invoking 728b the Npcf_SMPolicyControl_UpdateNotify service operation. For the UE group, if the PCF has already provided the SMF with CCP rules for individual UEs and the UE group, this step can be skipped. The PCF can use the UE group ID to send a message to the SMF to modify the CCP rules for all UEs in the same UE group.
[0097] [0097] According to the modalities, if the request type indicates "initial request" and step 725 has not been carried out, the SMF initiates an N4 session establishment procedure with the selected UPF, otherwise, it initiates a modification procedure session with the UPF selected. SMF 710 sends the 729a an N4 session establishment / modification request to the UPF and provides package detection, application rules and reporting to be installed on the UPF 708 for this PDU session. If the CN tunnel information is allocated by SMF, the CN tunnel information will be provided to the UPF at this stage. If the UE belongs to an UE group, the CN tunnel information may already be established for the UE group ID. The SMF sends a request to modify the N4 session to the UPF. The message includes the UE group ID, shared PDU session ID, UL TEID, DL TEID. If the UE belongs to an UE group and the CN tunnel is not established, the SMF sends an N4 Session establishment to the SMF. The message includes EU group ID, EU list (indicated, for example, by SUPI) in the EU group and CCP rules for individual EU and EU group. SMF can include DL TEID if SMF knows about the existing shared DL N3 tunnel. Otherwise, (R) AN can generate a new DL TEID at a later point. SMF can include a UL TEID. The UL TEID can belong to an existing shared N3 tunnel or a new non-shared N3 tunnel. UPF 708 confirms, by sending to 729b, an N4 session establishment / modification response. If the CN tunnel information is allocated by the UPF, the CN tunnel information will be provided to SMF at this stage.
[0098] [0098] According to some modalities, the SMF 710 can assign the same tunnel end point ID (TEID) for the N3 and N9 tunnels shared on the UL. If (R) AN assigns the DL N3 TEID, SMF can assign the same TEID to DL N9 TEID as DL N3 TEID. The (R) AN 704 and UPF 708 can perform bundling to send aggregated PDUs in the shared UL and DL N3 and N9 tunnels.
[0099] [0099] According to some modalities, if the UE PDU session has N3 and N9 tunnels not shared, SMF 710 can assign the same TEID for UL N3 and UL N9 tunnels. The (R) AN 704 can assign the TEID for the DL N3 tunnel, the SMF can use the same DL N3 TEID for the DL N9 TEID.
[00100] [00100] According to the modalities, SMF 710 sends 731 an Nsmf_PDUSession_CreateSM response that can include (cause, N2 SM information (PDU session ID, QoS profile (s), CN tunnel information, S-NSSAI, session -AMBR, UE group ID, QoS group profile (s), PDU shared session ID, DL TEID), N1 SM information (PDU session establishment acceptance (authorized QoS rule, SSC mode, S -NSSAI, allocated IPv4 address, AMBR-session))) for AMF 706. The N2 SM information carries information that the AMF must forward to the (R) AN to include one or more of the CN tunnel information that corresponds to the address of the central network of the N3 tunnel corresponding to the PDU session, the QoS profile provides the (R) AN with the mapping between QoS parameters and QoS flow identifiers. Multiple QoS profiles can be provided to the (R) AN, the ID PDU session can be used by AN signaling with the UE to indicate to the UE the association between AN resources and a session of PDU for the UE, the S-NSSAI is corresponding to the PDU session, the N1 SM information contains the PDU session establishment that accepts that the AMF must provide the UE, and the multiple authorized QoS rules can be included in the PDU session establishment accepted in N1 SM information and N2 SM information, the SM response also contains the PDU session ID and information that allows the MFA to know which UE is to be targeted, as well as to determine which access for the UE to use . It is understood that the access information is to deal with the case where a UE is connected simultaneously through 3GPP and non-3GPP access. The SMF must sign the UE location report in case of successful PDU session establishment, providing reporting criteria (for example, UE location in relation to the LADN availability area for a LADN). If the UE PDU session belongs to a shared PDU session, the SMF includes UE group ID and / or shared PDU session ID. If the UE is the first UE in an EU group that requests the establishment of a PDU session, the SMF also includes group QoS profiles. For other UEs of the same UE group ID and shared PDU session ID, the group QoS profile (s) may also include the DL TEID if the N3 tunnel is shared. The DL TEID is the TEID of the existing shared N3 tunnel. In addition, for some classes of devices, SMF cannot send one or more of the following to the UE in the NAS message: authorized QoS rule, SSC mode, S-NSSAI, allocated IPv4 address, AMBR session.
[00101] [00101] In accordance with the modalities, AMF 706 sends 731 an N2 PDU session request which can include (N2 SM information, NAS message (PDU session ID, PDU session establishment acceptance)) to (R ) AN
[00102] [00102] According to the modalities, the (R) AN 704 sends 733 an N2 PDU session response which can include (PDU session ID, cause, N2 SM information (PDU session ID, tunnel information (R ) AN, list of accepted / rejected QoS profiles (s))) for AMF 706. The tunnel information (R) AN corresponds to the N3 tunnel access network address corresponding to the PDU session. The UE can be assigned to a separate N3 tunnel or to a shared N3 tunnel. If SMF did not indicate DL TEID shared in step 730, (R) AN can include a DL TEID in the (R) AN tunnel information. If the UE belongs to an UE group ID and the shared N3 (R) AN tunnel for this UE group has been established, the N2 SM information can be omitted.
[00103] [00103] According to the modalities, AMF 706 sends 734 an Nsmf_PDUSession_UpdateSMContext request (N2 SM information) to SMF 710. AMF forwards the N2 SM information received from (R) AN to SMF. If the UE PDU session belongs to a shared PDU session ID and the SMF already has the shared (R) AN N3 tunnel information, this step can be skipped. If the N4 session for this PDU session has not yet been established, SMF initiates an N4 session establishment procedure with the UPF. Otherwise, SMF initiates an N4 session modification procedure with the UPF. SMF provides AN tunnel information and CN tunnel information. CN tunnel information only needs to be provided if SMF has selected CN tunnel information. If the request to establish a PDU session was due to the mobility between 3GPP and non-3GPP access, the downlink data path is switched to the destination access in this step. If the UE PDU session belongs to a shared PDU session and the SMF has already notified the UPF about (R) N3 shared tunnel information, this step and step 735b can be skipped. UPF 708 provides 735b an N4 session establishment / modification response to SMF.
[00104] [00104] According to some modalities, SMF 710 can assign the same tunnel end point ID (TEID) for the N3 and N9 tunnels shared on UL. If (R) AN assigns the DL N3 TEID, SMF can assign the same TEID to DL N9 TEID as DL N3 TEID. The (R) AN 704 and UPF 708 can perform bundling to send aggregated PDUs in the shared UL and DL N3 and N9 tunnels.
[00105] [00105] According to some modalities, if the UE PDU session has N3 and N9 tunnels not shared, SMF 710 can assign the same TEID for UL N3 and UL N9 tunnels. The (R) AN 704 can assign the TEID for the DL N3 tunnel, the SMF can use the same DL N3 TEID for the DL N9 TEID.
[00106] [00106] According to the modalities, SMF 710 sends 736 an Nsmf_PDUSession_UpdateSMContext response (cause) to AMF 706. After this step, AMF forwards relevant events to SMF, for example, in the transfer where the tunnel information (R ) AN are changed or the MFA is relocated. In addition, if step 734 is skipped, step 736 will also be skipped. In some modalities, in the case of a type of IPv6 PDU, the SMF 710 generates an IPv6 router advertisement and sends it to the UE 702 via UPF 708.
[00107] [00107] According to the modalities, if the request to establish a PDU session is due to a transfer between 3GPP access and non-3GPP access, that is, the type of request is defined as "existing PDU session", the SMF 710 takes steps to release 738 the user plan on source access (3GPP access or non-3GPP access). If the SMF identity is not included in the DNN signature context, be stored already in the SMF if it was previously registered or provided in steps 724a-724b by the UDM, the SMF 710 invokes 739 the Nudm_UEContextManagement_Update service operation including the SMF address, the DNN and the PDU session id. The UDM stores the SMF identity, the SMF address and the associated PDU DNN and session ID.
[00108] [00108] According to the modalities, if during the procedure the establishment of the PDU session is not successful
[00109] [00109] FIG. 8 illustrates UE or PDU session modification requested by the network for non-roaming and roaming with local interruption in accordance with the modalities of the present invention. UE 802 initiates the PDU session modification procedure by transmitting 821a of a PDU session modification request as a NAS message that can include (N1 SM information (PDU session modification request), PDU session ID ) message to the MFA
[00110] [00110] According to the modalities, the SMF 808 may need to report a signed event to PCF 814 invoking the service operation 822a Nsmf_EventExposure_Notify. PCF can provide new policy information to SMF by invoking the Npcf_SMPolicyControl_UpdateNotify service operation. This step can be skipped if the PDU session modification procedure was triggered in a previous step. If the dynamic PCC is not deployed, SMF can apply the local policy to decide whether to change the QoS profile. For the shared PDU session, the SMF uses the UE group ID and / or shared PDU session ID to report to PCF for signed events.
[00111] [00111] According to the modalities, steps 823 to 827 are not invoked when the modification of the PDU session requires only action in a UPF, for example, “gating”.
[00112] [00112] According to the modalities, for the modification initiated by UE, SMF 808 responds 823a to AMF 806 through Nsmf_PDUSession_UpdateSMContext (N2 SM information (PDU session ID, QoS profile, AMBR session), N1 information SM (PDU session modification command (PDU session ID, QoS rule, session-AMBR))). N2 SM information carries information that AMF must provide to (R) AN. This includes the QoS profiles that have been added, removed or modified. The N1 SM Container carries the PDU session modification command that the AMF must provide to the UE. For network initiated modification, SMF 808 invokes 823b Namf_Communication_N1N2MessageTransfer (SM N2 information (shared PDU session ID, PDU session ID, QoS profile, AMBR session, shared QoS profile, shared session AMBR), transmission N1 SM (PDU session modification command (PDU session ID, QoS rule, session-AMBR)) to the MFA
[00113] [00113] According to the modalities, AMF 806 can send 824 N2 session request (N2 SM information received from SMF, NAS message (PDU session ID, N1 SM information (PDU session modification command))) message to the (R) AN 804. The (R) AN 804 can issue 825 AN of specific signal exchange with the UE 802 which is related to the information received from the SMF. For example, in the case of a 3GPP RAN, a reconfiguration of the RRC connection can occur with the UE by modifying the necessary RAN resources related to the PDU session. The UE confirms the PDU session modification command by sending a NAS message (PDU session ID, N1 SM information message (PDU session modification command confirmation)). For shared PDU sessions, (R) AN uses the shared PDU session ID to identify the PDU sessions of the impacted UEs and apply the changes to all PDU sessions of the UEs.
[00114] [00114] According to the modalities, the (R) AN 804 can confirm the N2 PDU session request by sending 826 an N2 PDU session confirmation message (QFI (s), RAN tunnel information, NAS message, location information for AMF 806. In the case of dual connectivity, if one or more QFIs have been added to the PDU session, the master RAN node can assign one of these QFIs to a RAN node that was not previously involved in the PDU session, then the RAN tunnel information includes a new tunnel endpoint
[00115] [00115] According to the modalities, if the SMF interacted with the PCF in step 821c or 822a, SMF 808 notifies 829 to PCF 814 if the PCC decision could be applied or not invoking the Nsmf_EventExposure_Notify service operation. SMF can notify entities that have subscribed to user location information related to the change to the PDU session.
[00116] [00116] FIG. 9 illustrates a PDU session tunnel model according to the prior art. Current 3GPP systems, 3G / 4G / 5G, employ a PDU session tunnel between an (R) AN 902 and an UP 904. Each PDU session has two dedicated tunnels in UL 910, 920 and DL 912, 922. The UL and DL tunnels are reassigned when the UE moves to a new (R) AN node.
[00117] [00117] FIG. 10 illustrates a shared tunnel for a jump concept according to the modalities of the present invention. To avoid signal overload, the hop-on concept proposes that UP tunnels can be pre-configured, for example, UL 1010 shared tunnel and DL 1020 shared tunnel. When the UE is connected to the network, the UE can be associated with the tunnels pre-configured.
[00118] [00118] However, if the UPF needs the EU ID, represented by TEID for routing and traffic collection. When a shared tunnel is used, the EU ID can be carried in the tunnel header. This can increase the tunnel overhead. In addition, the UPF may need to know the UE location to forward DL packets. In the hop-on concept, the (R) AN can send a message to the UPF in the UL tunnel to inform the UPF of the new UE location. However, in 5G, the UE location update is performed in the CP. Thus, this may require signaling from (R) AN to AMF, then AMF to SMF, then SMF to UPF for UE location update.
[00119] [00119] FIG. 11 illustrates a hybrid PDU session tunnel according to the modalities of the present invention. According to the modalities, the UL and DL tunnel models may be different. For example, the UL tunnel can be shared tunnel 1110, while the DL tunnel is per PDU session tunnel, for example, DL PDU 1120 session tunnel and DL PDU 1122 session tunnel. This configuration may be appropriate for the scenario where all UPFs do not require UE ID to forward UL packets to the application server. The DL tunnel is not shared, so UE mobility can be easily addressed by the existing solutions already provided for in 3GPP systems. According to the modalities, it is desirable to support mobility UEs and the hybrid PDU session tunnel can provide for UL traffic from many UEs to be sent to the same application server using the pre-configured shared UP connections and the DL connection UP can be dedicated to each EU to support mobility.
[00120] [00120] According to the modalities, the NEF can be preconfigured by the network management function to serve one or more UE groups, one or more instances of network slice, one or more applications, one or more networks of local area data (LADN) and one or more data networks (DN). NEF can register with the NF repository (NRF) function. The NEF can be selected or re-selected by CP network functions, such as AMF or SMF or UDM or PCF or the NEF itself. The selection or re-selection of the NEF can be determined by one or more of: DNN, LADN, network slice information (for example, S-NSSAI), UE ID, UE location, UE group identifiers (by example, internal group ID, external group ID), EU group subscription information, SMF service area, UPF service area, AS location (for example, DNAI) and geographic zone identifiers, application ID.
[00121] [00121] To find out which AMF and SMF functions serve specific UEs, the NEF may need to access the UDM or UDR. According to the modalities, the NEF can send a notification message received from an AF to the UDM, PCF, AMF or service SMF to the UE group, instead of sending individual messages to each of the UEs. When the UE is registered on the network, the AMF accesses the UE subscription information in the UDM and / or UDR and knows about the UE Group ID and the pre-configured NEF. If it is the first EU in the EU group, the MFA can subscribe to the NEF event notification service for specific events, such as mobility information from the EU group. The AMF can register in the UDM that this AMF serves the EU group. When the UE requests the establishment of a PDU session, the AMF selects an SMF to serve the UE and / or the UE group that includes this UE. The SMF accesses the UDM to obtain UE subscription information as well as information about the UE group ID and the NEF function that serves the UE or the UE group. SMF can subscribe to NEF's event notification service for some events, such as AF requests for DNAI re-selection. The SMF can register in the UDM that this SMF serves the EU group.
[00122] [00122] According to the modalities, in some cases, due to UE mobility and / or application server mobility, or denial of service attack (DoS), or load balancing or NEF maintenance, and other reasons, a particular NEF may not be an optimal NEF to serve a particular EU or group of UEs and, as such, there may be a need to re-select the NEF for the EU group. For example, in a vehicle for all (V2X) situation, the UE or the entire UE group is indicative of the IoT devices associated with a specific vehicle and that vehicle is traveling. In this situation, the NEF can be used to send control messages or data from the AF or the application server (AS) of the V2X application to the specific UEs or all UEs in the UE IoT device group. While this vehicle is moving, the NEF may need to be selected again in order for the NEF to be positioned in a more suitable location along the vehicle's mobility path. In this example, a control plan function, for example, SMF can determine that re-selection of the NEF is necessary and proceed with the re-selection of a more suitable NEF. As another example, the need to re-select the NEF serving an EU group may be the result of load balancing. Other cases in which NEF re-selection may be necessary would be easily understood by a person skilled in the art.
[00123] [00123] FIG. 12 illustrates an example of a NEF selection or re-selection process serving a group of UEs. In this example, SMF 1223 determines 1201 that NEF re-selection is required and further selects a destination NEF 1225, for example, a NEF that is positioned in a more suitable location along a mobility path. SMF 1223 subsequently transmits 1202 a NEF relocation request to the originating NEF 1224. The originating NEF 1224 transmits 1203 an EU group context transfer to the destination NEF 1225 and the destination NEF 1225 transmits 1204 a confirmation of the same for the originating NEF 1224 of origin. Source NEF 1224 subsequently transmits 1205 a NEF update request to AF 1226 and AF 1226 subsequently transmits 1206 a response to the source NEF 1224. Source NEF 1224 transmits 1207 a context update request from UE group to UDM 1221. UDM 1212 transmits 1208 an EU group context change request to PCF 1220 and subsequently receives 1209 a response to it from PCF
[00124] [00124] Still taking into account FIG. 12, while it is illustrated that the UDM transmits requests for EU group context modification to the PCF and AMF, it will readily be understood that the originating NEF may transmit one or both of these EU group modification requests instead and subsequently receive the corresponding answer.
[00125] [00125] In current V2X platoon solutions, for example, when multiple UEs are traveling in the same vehicle, the application server selects a particular UE to be a leader for the plurality of UEs in the vehicle. In this configuration, the UE leader receives messages on behalf of the plurality of UE and the UE leader forwards those messages to the plurality of UE using device-to-device (D2D) links, for example PC5 side link in LTE. According to the modalities, when the plurality of UEs has been assigned to a UE group, the application server (AS) is able to communicate with each of the UEs within the UE group directly. However, for a transfer situation, for example, if the UE group is defined to include a plurality of UEs traveling in the same vehicle, the transfer can be carried out by transferring the UE group context from an originating RAN to a target RAN. In this modality, in the RAN or AN, all individual UEs are delivered to the destination RAN (T-RAN), where the source RAN (S-RAN) transfers the EU group context to the T-RAN and the T -RAN requests a path switch for all UEs using the UE group context, which can identify shared PDU sessions or non-shared PDU sessions or both. After switching the path, communication to all UEs in the UE group will pass through T-RAN. Since all UEs in the UE group can access the same data network (DN), the transfer delay associated with the transfer of all UEs by the transfer of the UE group context, when compared to the transfer of each of the UEs individually, would be essentially the same or less. However, it will be readily understood that the necessary signaling overhead that would be required to transfer all UEs in the group would be significantly reduced by transferring the EU group context instead of transferring each UE individually.
[00126] [00126] FIG. 13 illustrates a situation in which there is a single UE in the UE group, according to the modalities of the present invention. The UE 1310 in the vehicle is moving from an area served by an S- (R) AN 1301 to another area served by a T- (R) AN 1302. During the move, the UE 1310 can be served by different SMF, SMF Source (S-SMF) 1304 and Target SMF (T-SMF) 1305, and UPF, Source UPF (S-UPF) 1306 for Target UPF (T-UPF)) 1307. The T-SMF 1305 can select T-UPF 1307 to connect the UP path between T- (R) AN 1302 and the Destination DNAI (T-DNAI) 1308. S-DNAI 1311 provides UP access to Application Server 1, or Origin AS ( S-AS) 1312. T-DNAI 1308 provides UP access to Application Server 2 or Target AS (T-AS) 1309. The operation of ASs is coordinated by a 1340 moving edge computing (MEC) orchestrator. MEC 1340 orchestrator can exchange control messages with the CN 1315 via AFs, such as Source AF (S-AF) 1320 and Destination AF (T-AF)
[00127] [00127] According to the modalities, application servers and AFs can be part of the mobile edge computing platform (MEC). AF is the sound interface, providing a control link for the CN of the mobile network. DNAI represents an access point to the application's user plan on the MEC platform. There may be several local ASs that are geographically close to the UE site. AF can support one or more ASs. The NEF can be configured to be associated with one or more AFs and / or associated with one or more DNAIs and / or associated with one or more applications and / or associated with one of several DNNs and / or associated with one or more groups of UE and / or associated with one or more geographical area IDs and / or associated with one or more UPFs and / or associated with one or more registration areas and / or associated with one or more LADNs and / or associated with one or more AMFs and / or associated with one or more SMFs and / or associated with one or more PCFs and / or associated with one or more UDSF (unstructured data storage function) and / or associated with one or multiple UDM functions and / or associated with one or multiple UDR functions.
[00128] [00128] According to the scenario shown in Fig. 13, an NEF, such as T-NEF 1314, can be selected by an AF, such as T-AF 1321, based on the information obtained. Figure 14 can be considered an example. In the method, the T-AF 1450 can obtain information related to the UE in several ways, for example, by communicating with one or more functions, such as the S-AF 1460. Based on the information related to the UE, the T-AF 1450 can replace S-AF 1460 when subscribing to S-NEF 1420 event exposure services and transmitting an AF request related to influence on traffic routing, for example through a procedure that includes steps 1402 to 1405 To perform the selection of the T-NEF 1430, such as step 1406, the T-AF 1450 can obtain the NEF information in several ways, for example, a CAPIF function (common API structure) 1440, the NRF or the CP NFs such as AMF and SMF, which store NEF information locally. The selected T-NEF 1430 will replace the S-NEF 1420 to cooperate with the T-AF 1450 even further, for example, in subscribing to event exhibition services or in transmitting an AF request related to the influence on traffic routing or both, for example through a procedure that includes steps 1407 to 1410. FIG. 14 shows a method of selecting or re-selecting a NEF according to the modalities of the present invention. NEF is used for the exchange of CP messages between CN CP and AF functions, such as messages relating to requests to influence the routing of traffic or messages relating to membership in the event exhibition service. NEF can also be used to transfer data packets between the UE and the AF or AS. The method of FIG. 14 can be applied to individual UEs or groups of UEs. For example, when applied to individual UEs, AF can obtain UE contexts and when applied to a group of UE, AF can obtain the context of UE group.
[00129] [00129] In step 1401, S-AF 1460 transfers the UE context to T-AF 1450. The UE context stored in the AF contains all information related to the UE, such as external EU ID, external group ID, GPSI, S-NSSAI, S-NEF ID, UE location information, services currently subscribed to NEFs, such as S-NEF 1420, transaction ID (s) representing AF influence requests sent to S-NEF 1420 It will be understood that in some cases, step 1401 includes the transfer of the UE group context.
[00130] [00130] In an EU group context case, the EU group context may include the EU IDs that are in the EU group, the UE who is the leader (or group master or group head), the location of all UEs in the EU group. For example, the UE group context may include one or more UE group identifiers, one or more protocol data unit (PDU) session contexts and their PDU session identifiers, one or more session context shared protocol data unit (PDU) and its identifiers and a list of UE IDs that are members of the UE group.
[00131] [00131] In step 1402, the T-AF 1450 can subscribe to event display services of the S-NEF 1420, for example, as described in 3GPP TS 23.502, 4.15.3.2.3, and using the Nnef_EventExposure_Subscribe service in clause 5.2. 6.2.2, for the UE or UEs in the UE group.
[00132] [00132] In step 1403, T-AF 1450 can send the request for routing influence traffic to S-NEF 1420, for example, as described in 3GPP TS 23.502, clause 4.3.6.2, and using the service Npcf_PolicyAuthorization_Create on clauses 5.2.5.3.2, for the UE or UEs in the UE group.
[00133] [00133] In step 1404, the S-AF 1460 may cancel the subscription to event exhibition services of S-NEF 1420, for example, as described in 3GPP TS 23.502, clause
[00134] [00134] In step 1405, S-AF 1460 can cancel the AF-influenced traffic routing request on S-NEF 1420, for example, as described in 3GPP TS 23.502, clause 5.2.5.3.4 using the service Npcf_PolicyAuthorization_Delete, for the UE or UEs in the UE group.
[00135] [00135] In step 1406, T-AF 1450 may decide to select a new NEF. NEF information can be stored in a central CAPIF function (common API structure) 1440. NEF can provide its configuration information for the central CAPIF function using a procedure, for example, as described in clause 8.3 Published Service API of 3GPP TS 23.222, published in January 2018. The NEF can be configured to serve the entire PLMN network or some parts of PLMN, for example. The NEF can be selected based on one or more of the following information: PLMN ID, DNN, DNAI (s); applications, represented by application ID (s), Service-Identifier-AF; some network slice instances, represented by S-NSSAI or NSI-ID (network slice instance ID); EU group ID (s), such as internal group ID, external group ID, IMSI group ID; EU ID (s); AF, such as AF ID, IP address AF, AF FQDN; UPF address (UPF or FQDN IP address); AMF, such as AMF ID, AMF IP address, AMF FQDN; SMF, such as SMF ID, SMF IP address, SMF FQDN. For example, T-AF 1450 decides to select a new NEF based on the following conditions that may include: PLMN = 101, DNN = “Internet”, Service-Identifier-AF = “Application V2X-1”, S- NSSAI = 100 Assuming that the T-NEF 1430 is configured to serve V2X, where PLMN = 101, DNN = "Internet", Identifier-Service-AF = "Application V2X-1", S-NSSAI = 100, the T-NEF 1430 is the new NEF that is selected by the T-AF 1450.
[00136] [00136] The NEF configuration information can also be stored in the NRF, or stored locally in the CP NFs, such as AMF and SMF.
[00137] [00137] In step 1407, after selecting a T-NEF 1430, the T-AF 1450 can subscribe to T-NEF 1430 event exhibition services, for example, as described in TS 23.502, clause 4.15.3.2.3, and using the Nnef_EventExposure_Subscribe service in clause 5.2.6.2.2.
[00138] [00138] In step 1408, the T-AF 1450 can send requests for routing influence traffic to the T-NEF 1430, for example, as described in 3GPP TS 23.502,
[00139] [00139] In step 1409, the T-AF 1450 may cancel the subscription to event exhibition services of the S-NEF 1420, for example, as described in 3GPP TS 23.502, clause
[00140] [00140] In step 1410, the T-AF 1450 can cancel requests for routing AF-influenced traffic on the S-NEF 1420, for example, as described in TS 23.502, clause
[00141] [00141] In steps 1402 to 1405, 1407 to 1410, the S-NEF 1420 and the T-NEF 1430 may need to subscribe or unsubscribe to CP 1410 function network exposure services, such as UDM, AMF, SMF , PCF.
[00142] [00142] According to the modalities, the above procedure allows a T-AF 1450 to subscribe to the current S-NEF service
[00143] [00143] In some modalities, T-AF 1450 may not need to sign or send requests to S-NEF 1420. In this case, steps 1402 and 1403 are ignored. The T-AF 1450 subscribes to the event exhibition services of the T-NEF 1430 in steps 1404 and 1405. In this case, steps 1409 and 1410 are also ignored.
[00144] [00144] In some modalities, the same AF can serve the two application servers (S-AS and T-AS). The S-AF 1460 does not need to transfer the context information from UE to the T-AF 1450. Steps 1401 to 1405 are ignored. Steps 1406 to 1410 are performed with T-AF replaced by S-AF, since S-AF and T-AF are the same.
[00145] [00145] FIG. 15 illustrate another modality of re-
[00146] [00146] In step 1501, a series of triggers may require a NEF re-selection. For example, a trigger may be the result of one or more of: UE mobility event, when UE moves to a new location that is served by a new (R) AN node, during the transfer procedure, the SMF 1540 is notified by AMF 1530 about the new EU location; application mobility event, where the application server (AS) can be relocated to a new data center or to another computing machine in the same data center, AF can send AF-influenced traffic routing to SMF 1540 through PCF 1510; and load balancing between NEF, maintenance, relocation of S-NEF in data centers, denial of service (DoS) attack, a network management function such as the Operation, Administration and Management (OAM) function can inform the SMF 1540. For example, if the current NEF is highly loaded, the NEF can inform a CP NF, such as the SMF, to request re-selection of the NEF.
[00147] [00147] In step 1502, a CP NF, such as SMF 1540, decides to select another NEF to serve the UE or the PDU Session of the UE based on the triggers of step 1501. The SMF can interact with the NRF or a Central CAPIF Function to identify a suitable NEF. The CP, as SMF, can provide one or more of the following information for NRF or Central CAPIF Function: mobile network information, such as PLMN ID, DNN; network slice information, represented for example, S-NSSAI or NSI-ID; application information, such as service-identifier-AF, application ID, external application ID, internal application ID, DNAI information (for example, DNAI ID); UE information, such as internal group ID, IMSI group ID, external group ID, EU ID (for example, SUPI, GPSI); UE location information, such as (R) AN service node ID, (R) AN IP address or FQDN; AMF, SMF, PCF, UDM information service CP network role information (for example, network role ID or IP address or FQDN); and UPF information, for example the UPF ID, or your IP or FQDN address.
[00148] [00148] In some modalities, the S-NEF 1550 can initiate its own NEF re-selection. In this method, in step 1502, the S-NEF 1550 can interact directly with the NRF or Central Function CAPIF to identify a T-NEF. An NEF can have information stored locally to select another NEF.
[00149] [00149] In some modalities, the NRF or CAPIF Central Function can provide the list of possible NEFs that could serve the UE or the PDU session, along with attributes of the NEFs for the requested CP NF. NEF attributes can include one or more of the following information: mobile network information, such as PLMN ID, DNN; network slice information, represented for example, S-NSSAI or NSI-ID; application information, such as service-identifier-AF, application ID, external application ID, internal application ID, DNAI information (for example, DNAI ID); UE information, such as internal group ID, IMSI group ID, external group ID, EU ID (for example, SUPI, GPSI); UE location information, such as (R) AN service node ID, (R) AN IP address or FQDN; AMF, SMF, PCF, UDM information service CP network role information (for example, network role ID or IP address or FQDN); and UPF information: the UPF ID, or its IP address or FQDN. The NRF or CAPIF Central Function can return the list of NEFs that correspond to the information provided by SMF 1540 and, optionally, the NEFs load information. The load information can be the percentage of NEF resources being used.
[00150] [00150] In step 1503, if a NF CP, such as SMF 1540, sends a NEF relocation request to S-NEF, for example, a NEF relocation request. The request can include one or more of the following: CP NF ID (such as SMF ID, SMF IP address or FQDN); the T-NEF 1560 information (such as T-NEF ID, or IP address or FQDN); the time of beginning of NEF reallocation (time and immediate or scheduled date); the information to identify the UE: SUPI, GPSI and / or internal group ID, or an internal transaction ID associated with a previous request from AF 1570; information to identify the UE PDU session, such as the packet flow description (PFD); location information: for example, geographic area IDs; and the information to identify the application: for example, application ID, service-identifier-AF, DNAI.
[00151] [00151] In some modalities, the entire operation of the S-NEF 1550 can be transferred to the T-NEF 1560. In step 1503, the CP function, such as SMF 1540, can provide CP NF ID (such as SMF ID, address IP SMF or FQDN); the T-NEF 1560 information (such as T-NEF ID, or IP address or FQDN); the start time of NEF relocation (time and immediate or scheduled date) for the S-NEF 1550.
[00152] [00152] According to some modalities, CP NF, such as SMF 1540, may use a NEF service, namely the Nnef_UEContext_Relocation service described in this request, to send the NEF Relocation Request.
[00153] [00153] In step 1504, the S-NEF 1550 sends to the T-NEF 1560 an EU context transfer request, for example, an EU context transfer request (or EU group context). The request may include one or more of the following information: the S-NEF ID; time to start NEF re-selection: immediate or programmed; the context information of UE, which may include information related to UE, information related to AF, information about subscribed services of CP NFs and information in the user plan. According to the modalities, the information related to the UE may include one or more of the EU ID (SUPI, GPSI, IP address / prefix); mapping of SUPI to GPSI parameters; External group ID; external Group ID and IMSI Group ID mapping. According to the modalities, information related to AF can include one or more of Identifier-Service-AF (for example, edge computing applications); whether PA is authorized or not; identifier-service-AF parameter mapping and 5GC information (DNN, S-NSSAI) (for example, edge computing applications); mapping of identifier-service-AF parameter and a list of routing profile DNAI (s) and ID (s) (edge computing); mapping of parameters from the external application identifier to the corresponding application identifier known in PFDF (PFD management); AF request: mapping the internal AF transaction ID and AF transaction ID in the AF request (edge computing); AF subscription for monitoring events (for example, CN event display services): “NEF records the event trigger association and requester identity.”; and Trigger Quota or Rate (for example, SMS over NAS applications). According to the modalities, the information about the signed services of CP NFs may include one or more of the CP NF IDs that S-NEF has signed in its services: SMF ID, PCF ID, UDM ID, AMF ID and others; NEF stores AF notification report information received from AF and maps to NEF notification report information for PCF (s) (for example, edge computing applications); PCF signature for NEF notification about AF request (for example, in edge computing applications); NEF event subscription to monitor event exposure; event filters (for example, mass subscription services); AMF events, including mass subscription to many UEs (eg event exhibition service); and UDM events (for example, event exhibition services). According to the modalities, the information in the user plan may include one or more of the UPF which provides UP connection for transferring IoT messages between the AF / AS to the UE and the PDU session context of the UE using the S-NEF for communication with AF or AS.
[00154] [00154] According to some modalities, the S-NEF 1550 can use the Nnef_UEContext_Create described in this document to send the EU information from the S-NEF 1550 to the T-NEF 1560.
[00155] [00155] According to some modalities, the NEF can store the UE context on a local storage medium. Alternatively, NEF can store the UE context in an external storage function, such as UDSF (unstructured data storage function), UDR. If the UE context is stored in an external storage function, the S-NEF 1550 retrieves the UE context from the storage function and sends it to T-NEF 1560. Alternatively, the S-NEF 1550 can inform T-NEF 1560 the location of the UE context, which may include the network storage function address or ID (for example, UDSF IP address, UDSF ID, UDR ID, UDR IP address), the UE information (UE ID (GPSI, SUPI, external EU identifier)). In the case of the UE group, the S-NEF 1550 can include the internal group ID or external group ID.
[00156] [00156] According to some modalities, the S-NEF 1550 can also notify the CP function, such as UDM, SMF, AMF and PCF, of the location of the NEF UE context. This step is not shown in FIG 15. In the event that a DoS attack occurs on the S-NEF 1550, the SMF 1540 can directly send a NEF relocation request to the T-NEF 1560. This request can include the storage location of the EU NEF context for the T-NEF 1560 recover. In some scenarios, for example, a DoS attack scenario, NEF failure and some other scenarios, steps 1504, 1512, 1513, 1514, 1515 can be ignored.
[00157] [00157] According to the modalities, subsequently, the T-NEF 1560 can subscribe to the CP NFs services.
[00158] [00158] In step 1505, T-NEF 1560 can subscribe to the event exhibition service of SMF 1540, for example,
[00159] [00159] In step 1506, T-NEF 1560 can subscribe to the AMF 1530 event exhibition service, for example, using the service "Namf_EventExposure_Subscribe", as described in 3GPP TS 23.502, clause 5.2.2.3.
[00160] [00160] In step 1507, the T-NEF 1560 can subscribe to the UDM 1520 event exhibition service, for example, using the "Nudm_EventExposure_Subscribe" service, as described in 3GPP TS 23.502, clause 5.2.3.5.
[00161] [00161] In step 1508, T-NEF 1560 can subscribe to the event display service of PCF 1510, for example, using the "Npcf_Policy Authorization_Subscribe" service, as described in 3GPP TS 23.502, clause 5.2.5.3.
[00162] [00162] In step 1509, after completing all subscription services, the T-NEF 1560 sends to the S-NEF 1550, for example, the EU context transfer response (or EU group context), to confirm that the T-NEF is ready to serve the AF 1570. The T-NEF 1550 can use the Nnef_UEContext_Create described in this document to send the T-NEF 1560 Context Transfer Response UE to the T-NEF 1550.
[00163] [00163] In step 1510a, the S-NEF 1550 can send a message to request the AF to update the NEF information, for example, update the NEF request, for the AF 1570 so that the AF 1570 communicates with the new T-NEF
[00164] [00164] In step 1510b, AF 1570 can send a confirmation, for example, update the NEF response, to S-NEF 1550 to confirm receipt of the new NEF information. The AF 1570 uses the T-NEF 1560 to communicate with the NC NFs. If the S-NEF 1550 receives any notification messages from other CP functions related to the UE or PDU session that has been transferred to the T-NEF 1560, the S-NEF 1550 will not forward these messages to the AF 1570. This prevents the forwarding the same notification messages from S-NEF 1550 and T-NEF 1560 to AF 1570.
[00165] [00165] In some modalities, steps 1510a and 1510b can be implemented using an AF service, namely Naf_UEContext_Update, described in this document.
[00166] [00166] In the case of a DoS attachment, failure or maintenance of NEF, or some other scenarios, the T-NEF 1560, instead of the S-NEF 1550, sends a message in step 1510a to the AF. The message may include S-NEF and T-NEF 1560 identifiers, such as IP addresses or NEF IDs, a cause code indicating the reason for changing the NEF (e.g., DoS attack, NEF failure, NEF maintenance, load balancing, better packet delay) and transaction ID (s) that AF 1570 used to send AF influence traffic routing requests to the CN previously. In this case, the AF 1570 sends an update NEF response to the T-NEF 1560, instead of the S-NEF 1550.
[00167] [00167] In step 1511, the S-NEF 1550 can send a message for, for example, NEF Reallocation Response to the CP, such as SMF. This is to confirm that the newly selected T-NEF 1560 is ready to exchange CP messages or UP data packets with the AF 1570 or the application server.
[00168] [00168] According to some modalities, the S-NEF 1550 can use an NEF service, that is, the Nnef_UEContext_Relocation service described in this request, to send the NEF relocation response to the SMF 1540.
[00169] [00169] Subsequently, the S-NEF 1550 may cancel the subscription to the services of the CPNs.
[00170] [00170] In step 1512, T-NEF 1560 can unsubscribe from the SMF 1540 event exhibition service, using the "Nsmf_EventExposure_UnSubscribe" service, for example, as described in 3GPP TS 23.502, clause
[00171] [00171] In step 1513, the S-NEF 1560 can unsubscribe from the AMF 1530 event exhibition service, using the "Namf_EventExposure_UnSubscribe" service, for example, as described in 3GPP TS 23.502, clause
[00172] [00172] In step 1514, T-NEF 1560 can unsubscribe from the UDM 1520 event exhibition service, using the "Nudm_EventExposure_UnSubscribe" service, for example, as described in 3GPP TS 23.502, clause
[00173] [00173] In step 1515, the T-NEF 1560 can cancel the subscription to the PCF 1510 event exhibition service, "Npcf_Policy Authorization_UnSubscribe" service, for example, as described in 3GPP TS 23.502, clause
[00174] [00174] In FIG. 14 and FIG. 15, the UE context can be transferred or updated in AF. When using a service-based interface, AF can provide the following services to support transferring and updating UE context between two AF functions. AF services related to the UE context (for example, they can be named as Naf_UEContext) can include creating UE context (for example, they can be named Naf_UEContext_Create), UE context update (for example, they can be named Naf_UEContext_Update), release of UE context in AF (for example, which could be called Naf_UEContext_Release) and obtain the UE context of an AF (for example, which could be called Naf_UEContext_Get).
[00175] [00175] According to the modalities, the creation of EU context allows the creation of a new EU context in AF. The required entry can include EU ID (for example, GPSI, IMSI). The optional entry can include one or more UE location information, the subscription is notified about the change of session state of PDU, PEI, GPSI, AN type, NEF ID, EU related information (EU ID (SUPI , GPSI, IP address (es) / prefix (s))), whether authorized AF or not, transaction IDs (each corresponds to an AF request), AF Signature for Event Monitoring (event display) , information on the CPNs contracted services; CP NF IDs that S-NEF has signed for its services: SMF ID, PCF ID, UDM ID, AMF ID and others and event filters (for mass subscription). The necessary output from the UE context creation function is an indication of the result, for example, success or not, and in some modalities, an optional output can be a cause.
[00176] [00176] According to the modalities, the UE context update function can allow the updating of an existing EU context in AF. The entry can include EU ID (for example, GPSI, IMSI). The entry can optionally include one or more UE location information, the signature is notified about the change of session state of PDU, PEI, GPSI, AN type, NEF ID, EU related information (EU ID (SUPI , GPSI, IP address (es) / prefix (s))), whether authorized AF or not, transaction IDs (each corresponds to an AF request), AF Signature for Event Monitoring (event display) , information on the CPNs contracted services; CP NF IDs that S-NEF has signed for its services: SMF ID, PCF ID, UDM ID, AMF ID and others and event filters (mass subscription). The required output from the UE context update function is an indication of result, for example, success or not, and in some modalities, an optional output can be a cause or external UE ID or both.
[00177] [00177] According to the modalities, the release of EU context in the AF function can release an existing EU context in AF. The required entry can include EU ID (for example, GPSI, IMSI, external EU ID). The required output from the UE context release function is an indication of outcome, for example, success or not, and in some embodiments, an optional output can be an external UE cause or ID, or both.
[00178] [00178] According to the modalities, obtaining the EU context of the AF function can allow a consumer function to obtain the EU context in an AF. The required entry can include EU ID (for example, GPSI, IMSI). The necessary output from the AF obtaining UE context is an indication of result, for example, success or not success and UE context stored in AF. In some embodiments, an optional output can be a cause (for example, the UE context does not exist, the UE context cannot be transferred out of AF, UE ID (for example, external EU ID, GPSI).
[00179] [00179] According to the modality, the NEF services related to the UE context (for example, the service name can be Nnef_UEContext) include the creation of UE context in NEF (for example, which can be called Nnef_UEContext_Create), updating UE context in NEF (for example, which can be named Nnef_UEContext_Update), releasing of UE context in NEF (for example, which can be called Nnef_UEContext_Release), reallocation of UE context (for example, which can be called Nnef_UEContext_Relocation ) and obtain the UE context of a NEF (for example, which can be called Nnef_UEContext_Get).
[00180] [00180] According to the modalities, the creation of EU context in the NEF function can create a new EU context in the NEF. The required entry can include EU ID (for example, SUPI, GPSI, IMSI, 5G-GUTI). The optional entry can include one or more of: UE-related information: IP address / prefix, UE location (for example, RAN address) SUPI parameter mapping for GPSI, internal group ID, external group ID, mapping external group ID and IMSI group ID, external group ID and internal group ID mapping, packet flow description (PFD); AF-related information: identifier-service-AF, whether AF is authorized or not, identifier-service-parameter parameter mapping and 5GC information (DNN, S-NSSAI), identifier-service-parameter parameter mapping and an list of DNAI (s) and routing profile ID (s), parameter mapping of the external application identifier to the corresponding application identifier known in PFDF (PFD management); AF request: mapping the internal AF transaction ID and AF transaction ID in the AF request (edge computing); AF signature for event monitoring (event exposure): “NEF records the association of the event trigger and the identity of the requester.”; quota or trigger submission rate (SMS over NAS); information about subscribed ANC services; information in the user plan and in the context of the PDU session of the UE that uses the S-NEF to communicate with the AF or AS.
[00181] [00181] According to the modality, updating the UE context in the NEF function can update an existing UE context in the NEF. The required entry can include EU ID (for example, GPSI, IMSI). The optional entry can include one or more information related to the UE: IP address / prefix, UE location (for example, RAN address), parameter mapping from SUPI to GPSI, external group ID, external group ID mapping and IMSI group ID, packet flow description (PFD); AF-related information: identifier-service-AF, whether AF is authorized or not, identifier-service-AF parameter mapping and 5GC information (DNN, S-NSSAI), identifier-service-AF parameter mapping and a list of DNAI (s) and routing profile ID (s), parameter mapping of the external application identifier to the corresponding application identifier known in PFDF (PFD management); AF request: mapping the internal AF transaction ID and AF transaction ID in the AF request (edge computing); AF signature for event monitoring (event exposure): “NEF records the association of the event trigger and the identity of the requester.”; quota or trigger submission rate (SMS over NAS); information about subscribed ANC services; information in the user plan and in the context of the PDU session of the UE that uses the S-NEF to communicate with the AF or AS. According to the modalities, the information about the signed services of CP NFs may include one or more of the CP NF IDs that S-NEF has signed in its services: SMF ID, PCF ID, UDM ID, AMF ID and others; NEF stores AF notification report information received from AF and maps to NEF notification report information for PCF (s) (edge computing); PCF signature for NEF notification on AF request (edge computing); NEF event subscription to monitor event exposure; event filters (mass subscription); AMF events, including mass subscription to many event exhibition UEs); and UDM events (exhibition of events). According to the modalities, the information in the user plan can include the UPF that provides UP connection for the transfer of IoT messages between the AF / AS to the UE. The necessary output of creating UE context in the NEF function is an indication of result, for example, success or not, and in some modalities, an optional output can be a cause.
[00182] [00182] According to the modalities, the release of UE context in the NEF function can release an existing UE context in NEF. The required entry can include one or more of the following information: EU ID (for example, SUPI, GPSI, IMSI), internal group ID, external group ID, service-identifier-AF, network slice information (for example , S-NSSAI or NSI ID), location information (for example, geographic area IDs), CP function information (for example, PCF ID, SMF ID). The necessary output of the UE context release in the NEF function is an indication of the result, for example, success or failure, and in some modalities, an optional output can be a cause or external UE ID or both.
[00183] [00183] According to the modalities, the EU context relocation function can allow a consumer function to request the relocation of an existing EU context in the NEF to another NEF.
[00184] [00184] According to the modalities, obtaining UE context from an NEF function can allow a consumer function to obtain UE context in an NEF. The required entry can include one or more of the following information: information to identify CP NF requesting UE context reallocation (such as SMF ID, SMF IP address or FQDN); information to identify the network slice, for example, S-NSSAI, NSI-ID; information to identify the UE, for example, one or more of SUPI, GPSI, internal group ID, external group ID, and IMSI group ID; information to identify the AF request, for example, an internal transaction ID associated with a previous AF 1570 request; information to identify the UE PDU session, such as the packet flow description (PFD); location information (for example, geographic zone IDs, UPF service area, registration area, LADN service area, SMF service area, AMF service area); and information to identify the application (for example, DNN, application ID, AF service identifier, DNAI). The optional entry can include a cause. The necessary output of obtaining UE context from an NEF function is an indication of result, for example, success or not success and the UE context stored in NEF. In some embodiments, an optional output can be a cause (for example, the UE context does not exist, the UE context cannot be transferred outside of NEF), UE ID (for example, SUPI, GPSI).
[00185] [00185] NEF can provide a relocation service for other functions. This service can be called Nnef_Relocation. A consumer role can request the replacement of a source NEF with another destination NEF. The destination NEF obtains all UE context data from the source NEF or from a separate storage function, for example, the UDR or UDSF. The consumer role can send one or more of the following information to the destination NEF: the source NEF ID (or IP address, FQDN); EU information, for example, EU ID (for example, SUPI, GPSI, internal group ID, external group ID); storage function information (for example, source NEF ID, source NEF IP address, UDR ID or UDR IP address, UDSF IP, UDSF IP address); cause (for example, maintenance, DoS attack, load balancing). The target can send the result to the consumer function, which may include one or more of the following information: indication of the result (success, not success); cause (for example, UDR data query error). To fulfill the NEF relocation request, the destination NEF can access all UE context data from the supplied source that maintains the UE context data, such as the source NEF or a storage function. More details in this regard are explained in FIG. 16 as an example.
[00186] [00186] The central CAPIF function can provide notifications for CAPIF events. CAPIF events can be an out-of-service NEF instance (for example, due to network maintenance, hardware error, software error, DoS attack), an NEF instance is added, a NEF is replaced with another NEF.
[00187] [00187] AF can subscribe to notifications of CAPIF events. By subscribing to the CAPIF event, AF can provide its AF ID with an event filter, which can include PLMN ID, DNN, LADN, network slice information (such as S-NSSAI, NSI-ID), EU group (such as external group ID), application information (such as AF-service-ID, application ID), location information (such as geographic area ID), UE information (such as GPSI, external EU ID, IMSI), information NEF (like NEF ID, or API ID). CAPIF shall send CAPIF notifications to the signed AF when the conditions of the CAPIF events are combined with the event filter.
[00188] [00188] The UE NEF context of certain services, such as URLLC, can be stored in a separate storage function, such as UDSF. The NEF, which is responsible for supporting the UE connection, can inform the central CAPIF function of the location of the UE NEF context, such as the UDSF ID, IP address or FQDN. If an NEF instance is out of service for any reason, the CAPIF or AF can select another UE. CAPIF can provide the newly selected NEF instance with the location of the UE context so that the newly selected NEF is ready to serve AF requests without any interruption.
[00189] [00189] FIG. 16 illustrates a method for relocating an NEF according to the modalities of the present invention.
[00190] [00190] In step 1601, S-NEF 1650 stores the UE context, PDU session context or both in UDR 1645, for example, using UDR 1645 services. In the context of UE, PDU session context or both , is created for the first time, a service that can be called Nudr_UDM_Create, is used. If the UE context, PDU session context or both are already created, the S-NEF 1650 can use a service that can be called Nudr_UDM_Update to update the UE context, PDU session context or both.
[00191] [00191] In step 1602, the CAPIF 1665 central function decides to select another T-NEF 1660 again to replace the S-NEF 1650. The S-NEF 1650 may need to be selected again in certain scenarios, for example, DoS attack, failure of NEF, maintenance of NEF. In these scenarios, the network management function, such as the Operation Administration Management (OAM) function, can inform the CAPIF 1665 Central Function about the unavailability of the S-NEF 1650. Alternatively, the S-NEF 1650 can notify the Function Central CAPIF on its state (for example, DoS attack, NEF failure, NEF maintenance). This step is not shown in FIG. 16.
[00192] [00192] The S-NEF 1650 can also notify the Central Function CAPIF 1665 about its unavailability, by sending a request that can be called "Unpublished Service API", for example, as described in clause 8.4 of the 3GPP TS 23.222, published in January 2018. This step is not shown in FIG. 16.
[00193] [00193] In step 1603, the CAPIF 1665 Central Function can use the NEF_Relocation service to send the relocation request to T-NEF 1660.
[00194] [00194] In step 1604, T-NEF 1660 can obtain UE contexts if they are stored in a storage function, for example, using a service that can be called the UDR 1645 Nudr_UDM_Query service to obtain the UE context , PDU session context or both previously stored by S-NEF 1650.
[00195] [00195] In step 1605, the T-NEF 1650 can subscribe to the event notification services of CP functions, such as PCF 1610, UDM 1620, AMF 1630 or SMF 1640, for example, as previously described with reference in FIG. 15.
[00196] [00196] In step 1606, the T-NEF 1650 can send a response, for example, using NEF_Relocation Response to the Central Function CAPIF 1665 for step 1603.
[00197] [00197] In step 1607a, the CAPIF 1665 Central Function can send a message, for example, event notification, to the AF 1670 signed to inform the unavailability of the S-NEF 1650 and the replacement information T-NEF 1660, such as the ID or IP address of the T-NEF 1660.
[00198] [00198] In step 1607b, AF 1670 can send a message, for example, confirmation of event notification, to the Central Function CAPIF 1665 to reply to the message in step 1607a.
[00199] [00199] In step 1608, the T-NEF 1660 may cancel the subscription on behalf of the S-NEF 1650 of the event event notification services that the S-NEF 1650 has signed for the CP functions, such as PCF 1610, UDM 1620, AMF 1630 or SMF 1640, previously.
[00200] [00200] In step 1609, alternatively, the S-NEF 1650 can unsubscribe from the exhibition event notification services that the S-NEF 1650 has signed for the CP functions, such as PCF 1610, UDM 1620, AMF 1630 or SMF 1640, previously.
[00201] [00201] The method illustrated in FIG. 16 can have several advantages. First, the AF 1670 does not need to resend all AF-influenced traffic routing and subscription requests for network exposure event notification services in the event that the S-NEF 1650 is out of service. This would help to reduce service interruption times that the CN CP and AF functions cannot exchange control messages.
[00202] [00202] FIG. 17 is a block diagram of an electronic device (ED) 1701 illustrated within a computing and communication environment 1700 that can be used to implement the devices and methods disclosed herein. In some embodiments, the electronic device can be an element of a communications network infrastructure, such as a base station (for example, a NodeB, an evolved Node B (eNodeB or eNB), a next generation NodeB (sometimes referred to as a gNóB or gNB), a home subscriber server (HSS), a link bridge (GW), such as a packet link bridge (PGW) or a service link bridge (SGW), or various other nodes or functions within a central network (CN) or a public land mobility network (PLMN). In other modalities, the electronic device can be a device that connects to the network infrastructure through a radio interface, such as a cell phone, smartphone or another device that can be classified as a User Equipment (UE) In some embodiments, ED 1701 can be a machine-type communication device (MTC) (also referred to as a machine-to-machine device (M2M)) or other device that can be categorized with o UE although it does not provide a direct service to a user. In some references, an ED can also be referred to as a mobile device, a term intended to reflect devices that connect to the mobile network, regardless of whether the device itself is designed for, or capable of, mobility. Specific devices can use all the components shown or only a subset of the components, and the levels of integration can vary from device to device. In addition, a device can contain multiple instances of a component, such as multiple processors, memories, transmitters, receivers, etc. Electronic device 1701 typically includes a processor 1702, such as a central processing unit (CPU), and may further include specialized processors, such as a graphics processing unit (GPU) or other processor, 1703 memory, a 1706 network interface, and a bus 1707 for connecting the components of the ED 1701. The ED 1301 can optionally also include components, such as a mass storage device 1704, a video adapter 1705 and an I / O interface 1708 (shown in dashed lines).
[00203] [00203] The 1703 memory can comprise any type of non-transient system memory, readable by the 1702 processor, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), memory only (ROM), or a combination thereof. In one embodiment, memory 1703 may include more than one type of memory, such as ROM for use at startup and DRAM for program and data storage for use during program execution. The 1707 bus can be one or more of any type of various bus architectures, including a memory bus or memory controller, a peripheral bus or a video bus.
[00204] [00204] The electronic device 1701 can also include one or more network interfaces 1706, which can include at least one of a wired network interface and a wireless network interface. As illustrated in FIG. 17, network interface 1706 can include a wired network interface to connect to a 1712 network and can also include a radio access network interface 1711 to connect to other devices over a radio link. When ED 1701 is a network infrastructure element, the radio access network interface 1711 can be omitted for nodes or functions that act as PLMN elements other than those at the end of the radio (for example, an eNB). When ED 1701 is an infrastructure at the radio end of a network, wired and wireless network interfaces can be included. When the ED 1701 is a wirelessly connected device, such as user equipment, the 1711 radio access network interface may be present and may be complemented by other wireless interfaces, such as wireless network interfaces. The 1706 network interfaces allow the electronic device 1701 to communicate with remote entities, such as those connected to the 1712 network.
[00205] [00205] Mass storage 1704 can comprise any type of non-transitory storage device configured to store data, programs and other information and to make data, programs and other information accessible via the 1707 bus. Mass storage 1704 can comprise , for example, one or more of a solid state drive, hard disk drive, magnetic disk drive, or optical disk drive. In some embodiments, the mass storage 1704 can be remote to the electronic device 1701 and accessible through the use of a network interface, such as the interface
[00206] [00206] The optional video adapter 1705 and the I / O interface 1708 (shown in dashed lines) provide interfaces for coupling the 1701 electronic device to external input and output devices. Examples of input and output devices include a screen 1709 attached to the 1705 video adapter and an I / O 1710 device, such as a touchscreen attached to the 1709 I / O interface. Other devices can be attached to the 1701 electronic device and interfaces additional or less can be used. For example, a serial interface such as universal serial bus (USB) (not shown) can be used to provide an interface for an external device. Those skilled in the art will appreciate that in the modalities where ED 1701 is part of a data center, the I / O 1708 interface and the 1705 video adapter can be virtualized and delivered via the network interface.
[00207] [00207] In some modalities, the electronic device 1701 can be a standalone device, while in other modalities the electronic device 1701 can be resident within a data center. A data center, as will be understood in the art, is a collection of computing resources (usually in the form of servers) that can be used as a collective computing and storage resource. Within a data center, a plurality of servers can be connected together to provide a set of computing resources on which virtualized entities can be instantiated. Data centers can be interconnected together to form networks that consist of sets of computing and storage resources connected to each other by connectivity resources. Connectivity features can take the form of physical connections, such as Ethernet or optical communications links and, in some cases, can also include wireless communication channels. If two different data centers are connected by a plurality of different communication channels, the links can be combined using any of a number of techniques, including the formation of link aggregation groups (LAGs). It should be understood that any or all of the computing, storage and connectivity resources (along with other resources within the network) can be divided between different subnets, in some cases in the form of a resource slice. If resources in multiple connected data centers or another collection of nodes are sliced, different network slices can be created.
[00208] [00208] According to the modalities, a method is provided to manage the user equipment (UE) in a communication network. The method includes receiving, by a network function, a request from an UE, said UE belonging to an EU group and generating, by the network function, an EU group context for the EU group.
[00209] [00209] According to some modalities, the EU group context includes an EU group identifier. According to some modalities, the UE group context includes one or more protocol data unit (PDU) session identifiers. According to some embodiments, the UE group context includes one or more shared protocol data unit (PDU) session identifiers. According to some modalities, the EU group context includes a list of EU IDs that are members of the EU group.
[00210] [00210] According to the modalities, a method is provided to manage the user equipment (UE) in a communication network. The method includes receiving, via a network function, a request including indicative data from an EU group and transmitting, through the network function, a notification, the notification based on the request and the data.
[00211] [00211] According to some modalities, the data includes an EU group identifier. According to some embodiments, the data includes one or more protocol data unit (PDU) session identifiers. According to some modalities, the data includes one or more shared protocol data unit (PDU) session identifiers. According to some modalities, the request includes a request to modify a shared PDU session and in which the notification includes a rejection. According to some modalities, the request includes a request for relocation of the network exposure function (NEF) and where the notification includes data indicative of an EU group context and where the EU group context includes one or more of a UE group identifier, protocol data unit (PDU) session identifier and a shared PDU session identifier.
[00212] [00212] According to the modalities, a network function is provided including a network interface to receive data and transmit data to network functions connected to a network, a processor and a non-transitory memory to store instructions that, when executed by the processor, cause the network function to be configured to perform one or more of the methods defined above.
[00213] [00213] According to the modalities, when the UE is moving, the V2X Application Server can be relocated to meet the packet delay requirements. It is proposed to specify the NEF selection criteria to support domain management and minimize the delay in transferring control and possible data packages about the NEF.
[00214] [00214] Since the NEF is the interface for the exchange of control messages between the network functions AF and CN, it is important to make sure that the NEF is properly selected to minimize the delay of control messages and possible packets of data sent by NEF. For example, in V2X applications, many control messages sent from AS / AF to the UE depend on the location. If the UE location information is not sent quickly to the AF, the AF / AS may send incorrect control messages to the UE. Therefore, it is important to study the existing mechanisms for the selection of NEF and to identify possible problems for improvements.
[00215] [00215] According to the modalities, a basic NEF selection solution mechanism is provided. AF can discover NEF instances using the CAPIF structure. At the meeting SA WG2 # 125, SA WG2 agreed to support CAPIF
[2] [two]. Therefore, it is assumed that the work of SA2 in the discovery of NEF in 5GC must be carried out in parallel.
[00216] [00216] This solution addresses Main problem # 8 (Edge computing support). When a vehicle travels a long distance, the V2X Application Server (V2X AS) can be relocated together with the V2X UE in the vehicle to ensure low package delay requirements. FIG. 13 illustrates possible reallocations of the network and V2X AS functions along the trajectory of the UE. The MEC Orchestrator coordinates the operation of the V2X ASs. The CP messages between the MEC orchestrator and the CN are exchanged through the AF and NEF. NEF may be required as specified in clause 5.6.7 “Influence of Application Function on traffic”, TS 23.501
[7] [7]. The UP connection between the UE and the V2X AS is provided by an (R) AN, UPF and DNAI node. To support UE mobility, the following steps can be performed: 1) The mobile UE is now served by a different RAN node, 2) UPF and CP NFs can be re-selected, 3) V2X AS can be relocated. The 5GC provides methods for the CN and AF to negotiate DNAI, 4) NEF can be (re) selected.
[00217] [00217] Except for NEF selection, other selection or re-selection procedures have been specified (for (R) AN, AMF, UPF, DNAI) or under study (in the case of SMF). The UE can be transferred between RAN nodes as described in
[00218] [00218] Currently, the selection of NEF is not explicitly specified in TS 23.501 and TS 23.502. Anyway, according to the Common API Structure (CAPIF)
[10] [10] supported on 5GS, AF can discover NEF instances using CAPIF services. Multiple NEF instances can be assigned to serve one or more applications to mitigate potential denial of service (DoS) attacks, as well as to improve domain administration and signaling efficiency. AF can select a NEF to send requests to the CN and subscribe to network exposure events. NEF re-selection may be necessary to reduce the packet delay for control messages, as well as load balancing if necessary.
[00219] [00219] An NEF instance can be configured to serve one or more applications, one or more instances of Network Slice, one or more DNs, one or more geographical zones, one or more DNAIs, one or more UE groups. The NEF configuration information can be stored in the Central Function CAPIF, NRF or AF.
[00220] [00220] During the movement, the V2X UE can be served by a different set of CN functions in different administrative domains. If the V2X application knows the vehicle's trajectory, the V2X application can select different NEF instances, each for an administrative domain, to send requests for routing AF-influenced traffic and subscribe to CN event display services. These procedures can be performed at any time by the AF to make sure that the control link between the AF and the CN is ready to serve the UE whenever the UE enters an administrative domain.
[00221] [00221] AF can cancel AF Routing Traffic Routing requests and cancel the subscription of CN exposure events to an NEF when V2X UE is no longer in an administrative domain.
[00222] [00222] During the lifetime of a PDU session of a V2X application, the NEF can be (re) selected to support control messages exchanged between the CN and AF functions. FIG. 18 provides a high-level procedure for the (re) selection of NEF. AF is currently served by a Home NEF (S-NEF). The AF may want to connect to another Target NEF (T-NEF).
[00223] [00223] In accordance with the modalities of the present invention, this procedure is illustrated in FIG. 18.
[00224] [00224] In step 1801, if the AF has not yet discovered a T-NEF, AF discovers a set of T-NEF (s) using the CAPIF Central Function Service API Discovery as described in 3GPP TS 23.222, clause 8.7 [10]. AF can send the following query information for NEF discovery: DNN, S-NSSAI, external group ID and application information (geographic zone IDs, Service-Identifier-AF, DNAI).
[00225] [00225] In step 1802, AF can subscribe to Event Exhibition Services provided by T-NEF. AF can use Nnef_EventExposure_Subscribe provided by T-NEF to send event subscriptions to the CN.
[00226] [00226] In step 1803, AF can send a request to influence traffic routing to T-NEF using the Npcf_PolicyAuthorization_Create service described in clause 5.2.5.3.2, as part of the AF Influence Traffic Routing procedure in clause 4.3.6.2 of TS 23.502. T-NEF can perform the PCF discovery procedure to identify the service PCF.
[00227] [00227] In step 1804, the AF can cancel the subscription to S-NEF event exhibition services using the Nnef_EventExposure_Delete service, described in clause 5.2.6.2.3 of TS 23.502. S-NEF can cancel the network exposure services provided by UDM, AMF and PCF.
[00228] [00228] In step 1805, the AF can cancel the AF-influenced traffic routing requests previously sent to the S-NEF using the Npcf_PolicyAuthorization_Delete service, as described in clause 5.2.5.3.4 of TS 23.502.
[00229] [00229] The procedure in FIG. 18 uses some existing NEF services. The only necessary change is to specify the information that the NEF provides for the Central CAPIF Function for NEF (re) selection in TS 23.501 and TS 23.502, including: DNN, S-NSSAI, external group ID and application information (zone IDs geographic, Service-Identifier-AF, DNAI).
[00230] [00230] Additional work on NEF discovery can be specified in the CAPIF structure.
[00231] [00231] Although the present invention has been described with reference to specific characteristics and modalities thereof, it is evident that various modifications and combinations can be made without departing from the invention.
The specification and drawings should, therefore, be considered simply as an illustration of the invention, as defined by the appended claims, and are intended to cover any and all modifications, variations, combinations or equivalents that fall within the scope of the present invention.

权利要求:
Claims (37)
[1]
1. Method, characterized by the fact that it comprises: receiving, through a unified data management (UDM) of a network exposure function (NEF), a message including the information that identifies the UE group; and assign, by the UDM, an internal group identifier (ID) for the UE group, where the internal group ID is mapped to the information that identifies the UE group.
[2]
2. Method, according to claim 1, characterized by the fact that the UDM is selected by NEF.
[3]
3. Method according to claim 1 or 2, characterized by the fact that the information identifying the UE group comprises an external group identifier that identifies the UE group.
[4]
4. Method according to any one of claims 1 to 3, characterized in that the message further comprises a list of generic public signature identifiers (GPSIs), each GPSI identifying a member UE in the group of UEs.
[5]
5. Method according to any one of claims 1 to 4, characterized by the fact that the message indicates the UDM to create or modify or delete the UE group, the method further comprising: according to the message, perform, at least UDM, an action to create the EU group, modify the EU group or exclude the EU group.
[6]
Method according to any one of claims 1 to 5, characterized in that the message further comprises network slice information associated with the UE group, wherein the network slice information comprises an S-NSSAI.
[7]
7. Method according to any one of claims 1 to 6, characterized by the fact that the internal group ID is unique to the UE group.
[8]
8. Method according to any one of claims 1 to 7, characterized by the fact that the information identifying the UE group is used to create an EU route selection policy (URSP) for at least one of the EU member states in the EU group.
[9]
9. Method, according to claim 8, characterized by the fact that the creation of the URSP is carried out by a policy control function (PCF), preferably based on at least one of the information from each EU member in the group of EU or service subscription information.
[10]
10. Method according to any one of claims 1 to 9, characterized by the fact that the member UEs in the UE group are separated by the same session management function (SMF) selected by an access management function (AMF ) and / or the same user plan role (UPF) selected by a session management role (SMF).
[11]
11. Method according to any of claims 1 to 10, characterized by the fact that the information identifying the UE group is included in a request sent to NEF from an application function (AF).
[12]
12. Method, characterized by the fact that it comprises: receiving, through a network exposure function (NEF), a request, in which the request includes information that identifies a user equipment group (UE) that includes member UEs; and send, by NEF to a unified data management (UDM), a message to trigger the UDM to assign an internal group identifier (ID) to the UE group, where the message includes the information identifying the UE group and the internal group ID is mapped to the information that identifies the UE group.
[13]
13. Method, according to claim 12, characterized by the fact that it also comprises: selecting, by NEF, the UDM of a set of NEFs.
[14]
14. Method according to claim 12 or 13, characterized in that the information identifying the UE group comprises an external group identifier that identifies the UE group.
[15]
15. Method according to any of claims 12 to 14, characterized by the fact that the request further comprises: a list of generic public signature identifiers (GPSIs), each GPSI identifying a member UE in the group of UE; and / or a transaction ID that represents the request.
[16]
16. Method according to any one of claims 12 to 15, characterized by the fact that the message further indicates the UDM to create or modify or delete the UE group; and / or, the message also comprises a list of GPSIs included in the request; and / or network slice information associated with the UE group, wherein the network slice information comprises assistance information for single network slice selection (S-NSSAI).
[17]
17. Method according to any one of claims 12 to 16, characterized by the fact that the internal group ID is unique to the UE group.
[18]
18. Method according to any one of claims 12 to 17, characterized by the fact that the member UEs in the UE group are separated by the same session management function (SMF) selected by an access management function (AMF ), and / or, the same user plan role (UPF) selected by a session management role (SMF).
[19]
19. Method according to any one of claims 12 to 18, characterized by the fact that the request is received by the NEF for an application function (AF).
[20]
20. Method, characterized by the fact that it comprises: receiving, by a policy control function (PCF), at least one of the EU group's identification information, information from each EU member in the EU group, or signature information of service, and consequently create an EU route selection policy (URSP).
[21]
21. Method according to claim 20, characterized by the fact that at least one of the information identifying the UE group, information from each EU member in the UE group or service subscription information is received by the PCF of a unified data repository (UDR).
[22]
22. Method according to claim 20 or 21, characterized by the fact that the URSP is created for at least one EU member in the EU group and / or, for each EU member in the EU group.
[23]
23. Apparatus, characterized by the fact that it is configured to execute the method as defined in any one of claims 1 to 22.
[24]
24. System, characterized by the fact that it comprises a first apparatus configured to perform the method as defined in any of claims 1 to 11 and a second apparatus configured to perform the method as defined in any of claims 12 to
19.
[25]
25. Method, characterized by the fact that it comprises: sending, through an application function (AF) to a network function repository function (NRF), a request to discover network exposure function (s) (NEF (s) )); receive, by the NRF's AF, a response in which at least one of the request and response includes network slice information associated with the NEF (s) discovery (s); and select, by the AF, a NEF from the NEF (s) discovered based on the information received.
[26]
26. Method, according to claim 25, characterized by the fact that it further comprises: reinforcing, by the AF, the NEF selected to serve a user equipment (UE), in which the selected NEF is different from an original NEF that serves the UE before selecting the selected NEF.
[27]
27. Method according to claim 26, characterized by the fact that the AF selects the NEF of the discovered NEFs to serve the UE when receiving a trigger, the trigger resulting from one or more UE mobility, load balancing, relocation of a NEF, denial of service attack, a re-selection request.
[28]
28. Method according to any one of claims 25 to 27, characterized by the fact that the network slice information is represented by a unique network slice selection assistance information (S-NSSAI) and a network identifier. network slice instance (NSI-ID).
[29]
29. Method, according to any one of claims 25 to 28, characterized by the fact that the method further comprises: subscribing, by AF, the event exhibition services of the selected NEF.
[30]
30. Method, according to any one of claims 25 to 29, characterized by the fact that before the selection, the method further comprises: subscribing, by AF, event exhibition services of the originating NEF; and send, through AF, a request for routing influence traffic to the originating NEF; and after selection, the method also includes: canceling the subscription, by AF, of event exhibition services of the originating NEF; and cancel, by AF, the request for routing influence traffic with the originating NEF.
[31]
31. Method according to any one of claims 25 to 30, characterized by the fact that the information received further comprises: one or more among application information, UE information and AF identifier.
[32]
32. Method according to claim 31, characterized by the fact that the request information is represented by one of an AF service identifier, an application ID, an external application ID, an internal application ID, and information DNAI; and / or, the UE information is represented by one of an internal group ID, an IMSI group ID, an external group ID, an EU ID being preferably a SUPI and generic public signature identifier (GPSI).
[33]
33. Method according to any one of claims 25 to 32, characterized in that the request includes one or more of the following: application information and UE information for the NRF to discover the NEF (s).
[34]
34. Method, characterized by the fact that it comprises: receiving, through a network function repository function (NRF) from an application function (AF), a request to discover network exposure function (s) (NEF (s) )); obtain, by NRF, a record of the NEF (s); send, through the NRF to the AF, a response in which at least one of the request and the response includes network slice information associated with the discovery NEF (s).
[35]
35. Apparatus, characterized by the fact that it comprises means for carrying out the method as defined in any of claims 25 to 34.
[36]
36. Communication system, characterized by the fact that it comprises a first device configured to execute the method as defined in any of claims 25-33 and a second device configured to execute the method as defined in claim 34.
[37]
37. Non-transitory computer-readable medium characterized by the fact that it stores computer instructions, which when executed by one or more processors, cause one or more processors to perform the method as defined in any of claims 1 to 22 and 25 to 34.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112020016723A2|2020-12-15|SYSTEM AND METHOD FOR EU CONTEXT AND PDU SESSION CONTEXT MANAGEMENT

---

KR102167343B1|2020-10-19|System and method for application-friendly protocol data unit | session management

---

CN111480366B|2021-09-21|Shared PDU session establishment and binding

---

US10129108B2|2018-11-13|System and methods for network management and orchestration for network slicing

---

US11070627B2|2021-07-20|Discovery of a user plane function that supports cellular IoT optimization

---

US11224093B2|2022-01-11|Network initiated UPF sessions transfer

---

US10980084B2|2021-04-13|Supporting multiple QOS flows for unstructured PDU sessions in wireless system using non-standardized application information

---

US10123205B2|2018-11-06|Admission of a session to a virtual network service

---

US11019668B2|2021-05-25|PDU session establishment for cellular IoT

---

US11026080B2|2021-06-01|Policy control function determining method, apparatus, and system

---

JP6995189B2|2022-01-14|Data transmission methods, devices, and systems

---

US11166325B2|2021-11-02|Control plane based configuration for time sensitive networking

---

JP2019532581A|2019-11-07|Application service layer mobility management

---

KR102329156B1|2021-11-19|Methods and devices for selecting session management features

---

WO2021017381A1|2021-02-04|Systems and methods for supporting traffic steering through a service function chain

---

JP7004738B2|2022-01-21|Methods and equipment for session management function selection

---

WO2021052109A1|2021-03-25|Communication method and apparatus

---

US20210105196A1|2021-04-08|Support group communications with shared downlink data

---

WO2021087947A1|2021-05-14|A method for influencing data traffic routing in a core network

---

WO2021174189A1|2021-09-02|Session management for edge computing

---

CN110831086A|2020-02-21|Method, device and system for sending indication information and storage medium

同族专利:

---

公开号 | 公开日

---

EP3753298A4|2021-03-17|

---

US10999787B2|2021-05-04|

---

US20190261260A1|2019-08-22|

---

US20200154350A1|2020-05-14|

---

CN111771394A|2020-10-13|

---

EP3753298A1|2020-12-23|

---

WO2019158121A1|2019-08-22|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

JP2016503610A|2012-11-13|2016-02-04|ホアウェイ・テクノロジーズ・カンパニー・リミテッド|Method and network element for obtaining information about a packet|

---

US9471303B2|2015-02-04|2016-10-18|Sap Se|Façade framework for IDE|

---

EP3456090B1|2016-05-12|2021-03-31|Convida Wireless, Llc|Connecting to virtualized mobile core networks|

---

US10362507B2|2016-06-10|2019-07-23|Huawei Technologies Co., Ltd.|Systems and method for quality of service monitoring, policy enforcement, and charging in a communications network|

---

US10212639B2|2016-07-26|2019-02-19|At&T Intellectual Property I, L.P.|Method and apparatus for dynamic data path selection for narrow band wireless communication|

---

US10455641B2|2017-01-05|2019-10-22|Huawei Technologies Co., Ltd.|Protocol data unit management|

---

TWI655877B|2017-02-06|2019-04-01|財團法人工業技術研究院|User equipment registration method for selecting network slicing, and network controller and network communication system using the method|

---

US10952176B2|2017-03-17|2021-03-16|Samsung Electronics Co., Ltd.|AF influenced PDU session management and subscription procedures|

---

US10447370B2|2017-11-07|2019-10-15|Intel IP Corporation|Systems, methods and devices for using s-Measure with new radio|

---

US10110495B1|2017-11-22|2018-10-23|Intel Corporation|Multi-access edge computing service provision based on local cost measurements|US10736072B2|2016-11-27|2020-08-04|Lg Electronics Inc.|De-registration method in wireless communication system and apparatus therefor|

---

US10797894B2|2017-12-28|2020-10-06|Ofinno, Llc|Service type and device type-based policy and charging control|

---

WO2019183978A1|2018-03-31|2019-10-03|Intel Corporation|Technologies for content delivery network with multi-access edge computing|

---

CN111919456A|2018-04-05|2020-11-10|三星电子株式会社|Method and device for providing local area data network service based on non-subscription model in wireless communication system|

---

US20190313310A1|2018-04-09|2019-10-10|Nokia Technologies Oy|Session context conversion|

---

US20190313311A1|2018-04-09|2019-10-10|Mediatek Inc.|Apparatuses, service networks, and methods for handling plmn-specific parameters for an inter-plmn handover|

---

US11178717B2|2018-05-21|2021-11-16|Electronics And Telecommunications Research Institute|Traffic distribution method through multi-access network in a network and network entity performing the same|

---

CN110519074A|2018-05-22|2019-11-29|华为技术有限公司|A kind of coverage management method and device|

---

US11243978B2|2018-06-29|2022-02-08|EMC IP Holding Company LLC|Non-centralized data synchronization for IoT and other distributed applications|

---

US10750553B2|2018-09-25|2020-08-18|Cisco Technology, Inc.|Systems and methods for selection of collocated nodes in 5G network|

---

KR20200039412A|2018-10-05|2020-04-16|삼성전자주식회사|Method and apparatus for transmission and reception of data in wireless communication system|

---

KR20200039306A|2018-10-05|2020-04-16|삼성전자주식회사|Method and apparatus for provisioning service parameters to the ue and the network in 5g system|

---

US10708716B2|2018-10-16|2020-07-07|Cisco Technology, Inc.|Methods and apparatus for selecting network resources for UE sessions based on locations of multi-access edge computingresources and applications|

---

US10827537B2|2018-12-03|2020-11-03|At&T Intellectual Property I, L.P.|Network core software defined networking enabled onboarding of micro services for an advanced wireless communications system|

---

US10938996B2|2019-03-22|2021-03-02|T-Mobile Usa, Inc.|Controlling services provided to mobile devices within wireless communication networks|

---

US11197232B2|2019-04-01|2021-12-07|Ofinno, Llc|Location reporting handling|

---

US11252652B2|2019-04-02|2022-02-15|Electronics And Telecommunications Research Institute|Non-IP data delivery authorization update method and connection release method for non-IP data delivery, and device for performing the method|

---

US10924893B2|2019-04-16|2021-02-16|Verizon Patent And Licensing Inc.|Group message delivery using multicast|

---

US10917764B2|2019-05-02|2021-02-09|GM Global Technology Operations LLC|System and method to responsively send vehicle information to a data center|

---

KR20200131149A|2019-05-13|2020-11-23|삼성전자주식회사|Method and apparatus for supporting service in wireless communication system flexibly|

---

TWI721923B|2019-08-02|2021-03-11|華碩電腦股份有限公司|Method and apparatus for releasing sidelink radio bearer in a wireless communication system|

---

WO2021037386A1|2019-08-30|2021-03-04|Nokia Technologies Oy|Enhancements of registration of nef at nrf|

---

KR20210027976A|2019-09-03|2021-03-11|삼성전자주식회사|Method and apparatus for providing multicast and broadcast service in mobile communication network|

---

WO2021052761A1|2019-09-20|2021-03-25|Telefonaktiebolaget Lm Ericsson |Methods and apparatuses for event exposure of location reporting for a terminal device|

---

WO2021066346A1|2019-10-02|2021-04-08|엘지전자 주식회사|Method for moving pdu session on non-3gpp to 3gpp access|

---

WO2021089905A1|2019-11-04|2021-05-14|Nokia Technologies Oy|Dynamically unsubscribing from a plmn/npn service|

---

CN110996322B|2019-11-28|2021-07-30|楚天龙股份有限公司|Method for realizing secondary authentication of terminal|

---

WO2021103016A1|2019-11-29|2021-06-03|华为技术有限公司|Packet transmission method, communication device, and communication system|

---

WO2021126029A1|2019-12-19|2021-06-24|Telefonaktiebolaget Lm Ericsson |Method and apparatus for signaling session terminations in a communication network|

---

EP3855803A1|2020-01-22|2021-07-28|Nokia Solutions and Networks Oy|Group handover between logical radio networks|

---

WO2021159523A1|2020-02-14|2021-08-19|华为技术有限公司|Communication method, apparatus and system|

---

US20210274392A1|2020-02-27|2021-09-02|Huawei Technologies Co., Ltd.|Methods, systems and apparatuses for management or network functions|

---

WO2021194323A1|2020-03-27|2021-09-30|삼성전자 주식회사|Session management method according to application of user equipment policy in wireless communication system|

---

CN113498215A|2020-04-08|2021-10-12|中国移动通信有限公司研究院|Method and equipment for opening network information|

---

CN111511044A|2020-04-16|2020-08-07|蓓安科仪（北京）技术有限公司|Data communication method for realizing telemedicine based on 5G network|

---

US11265698B2|2020-04-22|2022-03-01|T-Mobile Usa, Inc.|Access and mobility functiondata storage in cellular network registration|

---

KR20210144205A|2020-05-21|2021-11-30|삼성전자주식회사|Method and apparatus for establishing a session in a wireless communications system supporting network slicing|

---

CN113873478A|2020-06-30|2021-12-31|华为技术有限公司|Communication method and device|

---

WO2022019486A1|2020-07-21|2022-01-27|엘지전자 주식회사|Method and apparatus for providing network slice services through multi-operator networks in wireless communication system|

---

WO2022036100A1|2020-08-12|2022-02-17|Idac Holdings, Inc.|Methods and apparatuses for discovery and selection of a local nef|

法律状态:
2021-12-07| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

US15/898,442|2018-02-17|

---

US15/898,442|US10999787B2|2018-02-17|2018-02-17|System and method for UE context and PDU session context management|

---

PCT/CN2019/075177|WO2019158121A1|2018-02-17|2019-02-15|System and method for ue context and pdu session context management|

---